Skip to main content
Glama

datovka_list_received

Destructive

Lists received messages in a selected Czech data box, with optional date filtering and result limits. Use it to review incoming mail; it may trigger delivery and requires enabled receiving.

Instructions

Nacte prijate zpravy. Muze zpusobit doruceni; vyzaduje povoleny prijem.

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>"
    },
    "name": "datovka_list_received"
  }
}

Input Schema

NameRequiredDescriptionDefault
box_aliasYes
from_dateNo
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior4/5

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

With readOnlyHint=false and destructiveHint=true, the annotations already flag a non-trivial side effect; the description earns credit by explaining the mechanism ("muze zpusobit doruceni" – may cause delivery) and the precondition. It remains vague about what exactly gets delivered or changed, so it is not fully transparent, but it neither repeats nor contradicts the annotations.

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, front-loaded sentences with no filler; the side-effect warning is placed correctly after the purpose clause. It loses a point only because the extreme terseness (and Czech phrasing) leaves key terms like "doruceni" unexplained for an agent operating in an English toolset.

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

Completeness2/5

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

For a tool with a real side effect, three undocumented parameters, and no parameter coverage in the schema, the description is thin – it neither bounds the date range nor explains the alias or result cap (the output schema covers return values, so that part is fine). It is adequate for a human familiar with Datovka but not for an agent choosing and parameterizing the call.

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% across three parameters (box_alias, from_date, max_results), and the description supplies nothing to compensate – no meaning for the alias, no date format/range behavior, no note on the default of 50 results or pagination. The description adds zero parameter meaning beyond the bare schema titles.

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?

"Nacte prijate zpravy" states a specific verb (load) plus resource (received messages), which clearly separates it from siblings such as datovka_list_sent or datovka_list_boxes. It stops short of the 5 bar because it never explicitly contrasts itself with those siblings and the verb is somewhat ambiguous between "read" and "trigger download."

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

Usage Guidelines3/5

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

The prerequisite "vyzaduje povoleny prijem" (requires receiving enabled) is real usage guidance an agent can act on before calling. However, there is no statement of when to prefer this over datovka_search_box or datovka_read_message, and no exclusion of any case, so usage is only implied by the name.

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