Skip to main content
Glama
Sign In
idoklad-mcp

idoklad-mcp

by honzsik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get credit note

get_credit_note
Read-only

Retrieve full details of a credit note by its ID, including line items, partner data, and prices. Use it to inspect a specific credit note in iDoklad.

Instructions

Get full detail of one credit note (opravný daňový doklad / dobropis) by ID, including items, partner and prices.

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": {
      "id": "<id>"
    },
    "name": "get_credit_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument ID (not the document number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and not contradicted. The description adds value by sketching the payload ('items, partner and prices'), which matters because there is no output schema. It says nothing about permissions, error behavior for an unknown ID, or whether the result includes related documents, so it is solid but not rich.

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

Conciseness5/5

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

A single front-loaded sentence with the scope ('one credit note by ID') stated before the payload contents. Nothing is redundant, and the bilingual domain terms earn their space by aiding term matching.

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

Completeness4/5

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

For a one-parameter read tool whose annotations cover safety and whose schema covers the argument, this is nearly complete; the description even compensates for the absent output schema by naming the main returned components. A brief note on error handling for invalid IDs or on linked documents would make it fully complete.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage, and the schema already carries the critical disambiguation ('Document ID (not the document number)'). The description's 'by ID' adds no meaning beyond that, which matches the baseline 3 for high-coverage schemas.

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?

Uses a specific verb and resource: retrieve the full detail of a single credit note by ID, which implicitly contrasts with the sibling list_credit_notes. The parenthetical Czech terms (opravný daňový doklad / dobropis) further pin down the domain object. It does not explicitly name a sibling, so it sits at 4 rather than 5.

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 wording 'by ID' implies you should call this when you already hold a document ID and want detail rather than a list, but there is no explicit when-to-use statement, no prerequisite (e.g., where to obtain the ID), and no named alternative. Usage is inferable rather than stated.

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

Deploy Server

Other Tools