Skip to main content
Glama

datovka_list_sent

Destructive

Lists sent messages from a selected data box account, with optional date filtering and result limits for reviewing outgoing correspondence.

Instructions

Nacte odeslane zpravy z vybraneho uctu. Vyzaduje povoleny sitovy 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_sent"
  }
}

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

C2.5/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 load of sent messages, which reads as a safe retrieval, while annotations declare readOnlyHint=false and destructiveHint=true. That is a direct inconsistency an agent could act on incorrectly. The one genuinely additive detail, the network-reception prerequisite, does not offset the conflict.

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 the operation stated first and the prerequisite second; nothing is padded or redundant. The brevity is only a problem because content is missing, not because of wasted wording.

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?

An output schema exists, so return values need no explanation, but with three undocumented parameters, no pagination behavior for max_results, no date-format guidance for from_date, and a safety profile that conflicts with the annotations, the definition is not sufficient to call the tool correctly.

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 parameter meaning, and it largely does not. "Vybraneho uctu" loosely implies box_alias, but from_date and max_results (default 50) are never mentioned, leaving date filtering and result limiting undocumented anywhere.

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 ("Nacte odeslane zpravy" = loads sent messages) and scopes it to a selected account. This clearly separates it from datovka_list_received and datovka_list_boxes, though it never names those siblings explicitly.

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?

The only guidance is a prerequisite ("Vyzaduje povoleny sitovy prijem" – requires network reception enabled). There is no statement of when to use this versus datovka_search_box for filtering, or versus datovka_list_received, and no exclusions or edge cases.

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