Skip to main content
Glama

datovka_read_message

Destructive

Downloads a received data box message with base64-encoded attachments using a box alias and message ID; retrieving it may trigger delivery.

Instructions

Stahne prijatou zpravu s prilohami base64; muze zpusobit doruceni.

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

Input Schema

NameRequiredDescriptionDefault
box_aliasYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds the concrete, non-obvious side effect behind that flag: reading "muze zpusobit doruceni" (may cause delivery), i.e. the read has an irreversible state-changing consequence. It also discloses that attachments come back base64-encoded, which matters for downstream handling. It stops short of explaining what delivery means operationally or whether it can be undone.

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?

A single compact sentence with no filler, and the side-effect warning is placed in a trailing clause where it is visible. Brevity is close to the lower limit, but nothing is wasted or buried.

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 two-parameter tool with no output schema, the description covers the key risk (delivery side effect) and the attachment encoding, which is the most important information. It is still incomplete on return structure, error cases, and parameter meaning, and it is written in Czech while sibling tool names are English, which may hinder matching.

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% and both parameters (box_alias, message_id) are required, so the description carries the full burden. It says nothing about what a box alias is, whether message_id is scoped to that box, or what format either takes, adding no meaning beyond the bare schema.

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 ("Stahne prijatou zpravu s prilohami base64" = downloads a received message with attachments in base64), so an agent knows exactly what the operation fetches. It does not, however, distinguish this from siblings such as datovka_list_received or datovka_get_draft, so the agent must infer which retrieval tool applies.

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 explicit when-to-use statement, no prerequisite (e.g. message must be in a received box), and no pointer to an alternative tool. Usage is only implied by the word "prijatou" (received), leaving the agent to guess the boundary against list/search siblings.

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