Skip to main content
Glama

datovka_list_boxes

Read-only

Lists locally configured Czech data box accounts without connecting to ISDS or requiring login credentials.

Instructions

Mistni seznam uctu bez pripojeni k ISDS a bez prihlasovacich udaju.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datovka_list_boxes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond them: this works on local data with no ISDS connection and no authentication, which tells the agent no credentials or network are needed. It stops short of saying what is returned or whether results reflect only cached/offline state.

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 short sentence with no filler, and the key constraint (local, no ISDS, no credentials) is front-loaded. The mixed Czech/English naming and the 'uctu' vs 'boxes' wording cost it a point on clarity.

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 zero-parameter read tool with full annotations and an output schema, the essentials are present. What is missing is any statement of how the listed accounts relate to the other listing tools or what 'boxes' means in this client, so the agent has to guess at scope.

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

Parameters4/5

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

With zero input parameters there is nothing to disambiguate, so the baseline of 4 applies. The description correctly implies a no-argument local listing.

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 concrete verb/resource pair ('Mistni seznam uctu' = local list of accounts) and implicitly separates itself from network-backed operations. It is slightly weakened by calling the resource 'uctu' (accounts) while the tool name says 'boxes', and by being written in Czech while the tool name and siblings are English, so an English-reading agent must translate to confirm the mapping.

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?

It implies the usage condition (callable without ISDS connectivity or login credentials), which is useful context for selection, but it never names or contrasts with any sibling such as datovka_list_received, datovka_list_sent, or datovka_search_box. The agent must infer when this offline listing is preferred over the other listing tools.

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