Skip to main content
Glama

datovka_search_box

Destructive

Search recipients within an explicitly selected Czech data box account by query, ensuring results stay tied to the intended account.

Instructions

Vyhleda prijemce pres explicitne zvoleny ucet. Zadny ucet se nehada.

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": {
      "box_alias": "<box_alias>",
      "query": "<query>"
    },
    "name": "datovka_search_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
box_typeNo
box_aliasYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior1/5

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

The description frames the operation as a plain lookup ("vyhleda"), while annotations declare readOnlyHint=false and destructiveHint=true. A read-styled search described against destructive, non-read-only annotations is a direct conflict, and the description does nothing to explain what could be modified, what authorization the chosen account needs, or that the call reaches an external registry (openWorldHint=true).

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

Conciseness4/5

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

Two short sentences with no filler, and the hard constraint is placed after the action so the operation is read first. It is efficient, though the extreme terseness leaves no room for the missing detail noted elsewhere.

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?

An output schema exists, so return values need not be explained. However, for a three-parameter, open-world tool with zero schema coverage and a destructive annotation, the description omits what box_type selects, what query matches against, and any side effects of the call, leaving real gaps.

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?

Schema description coverage is 0%, so the description must carry the parameter burden and it only partially does: it clarifies that box_alias must be an explicitly supplied account rather than guessed. The query parameter and the optional box_type (its allowed values, its default of null, its effect on the search) receive no meaning at all.

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

Purpose3/5

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

"Vyhleda prijemce" states a search action and a target, but the object is ambiguous against the tool name: the tool is called search_box while the description says it searches recipients (prijemce). Nothing distinguishes it from datovka_list_boxes or the message-reading siblings, so an agent knows roughly what it does but not exactly what it returns.

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?

"Zadny ucet se nehada" is a constraint on input (the account must be given explicitly, never inferred), not guidance about when to pick this tool over the listing siblings. No when-to-use, no prerequisites, no alternatives are stated.

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