Skip to main content
Glama

Briefe durchsuchen

letter_search
Read-only

Durchsucht die Briefe des Partners per Freitext über Betreff, Empfängername und Briefinhalt. status ist der Briefstatus; vor dem Auftrag trägt ein Brief in der Freigabe denselben Status wie in order_status: pending_approval, approved_in_grace oder queued_autopilot, dazu approval mit approvalId. letterStatus ist der gespeicherte Briefstatus. EN: Full-text searches the partner's letters across subject, recipient name and letter content. status is the letter status; before the order exists, a letter in the approval queue carries the same status as in order_status: pending_approval, approved_in_grace or queued_autopilot, plus approval with its approvalId. letterStatus is the stored letter status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "letter_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoStandard 20, maximal 100. EN: Default 20, maximum 100.
queryYes
sinceNoNur Briefe, die seit diesem Zeitpunkt geändert wurden (ISO 8601). EN: Only letters modified since this time (ISO 8601).
offsetNoVersatz für die Seitennavigation. Standard 0. EN: Offset for pagination. Default 0.
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description is consistent with it. It adds no behavioural detail of its own about result ordering, pagination behaviour, or what a match set looks like; the status exposition is domain semantics rather than behaviour.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and clear, but the body is duplicated wholesale in German and English and is dominated by a dense status/order_status explanation that does not map to any callable parameter. Roughly half the text does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter read-only search with no output schema, the search-scope coverage is adequate and annotations carry the safety profile. But the unexplained 'reasoning' parameter and the phantom status parameters leave gaps an agent would have to guess around.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description usefully explains what the required 'query' searches over, which the schema leaves bare. However it then spends most of its length on 'status' and 'letterStatus' parameters that do not exist in the input schema, while 'reasoning' goes undocumented — with additionalProperties=false this risks an agent sending a rejected parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Full-text searches the partner's letters') and enumerates the searched fields (subject, recipient name, letter content), which is enough to separate it from letter_list and letter_get. It stops short of naming those siblings explicitly, so it lands just below the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this tool versus letter_list, letter_get, or document_list, and no prerequisites or exclusions are given. The only guidance is implicit in the word 'search'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.