AthausDocs

MCP tools: how they are built

How the tools of the two MCP servers are built. The lists themselves are per server.

Last updated:

Each server has its own list, ordered by the right a tool requires.

The names

English, snake_case, verb first; what a person reads (titles, descriptions, results) is German. search_ searches with free text and filters, list_ reads small sets from your account, get_ fetches one thing with its context, save_ creates without an ID and changes with one, update_ only changes. draft_, send_ and decide_ can let something go out: they prepare, your click carries out.

The same name can mean different things on the two servers: get_inquiry is an enquiry to your office on Athaus für Anbieter, your enquiry about a listing on the search server. Values in inputs are English (buy, rent).

What a tool returns

The server describes inputs and outputs in tools/list. A result has a text that is complete on its own (when an assistant shows an interface, its model only sees this), the same data as structuredContent and, for whatever waits for a click, confirmation. An error comes back as a result with isError, a sentence naming the next step and the error code in _meta["athaus/code"]; if a detail is missing, it asks exactly one question.

Hints for models

The server sends the protocol's hints: readOnlyHint for tools that only read, destructiveHint where a call replaces, deletes, discards, revokes or irreversibly sends something (not for creating something new), openWorldHint where a tool asks outside services or sends something out itself. Anything that goes out is carried out by a person's click (Rights).

Keep reading

On this page