Skip to main content
Glama
Sign In
idoklad-mcp

idoklad-mcp

by honzsik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get received invoice

get_received_invoice
Read-only

Retrieve complete details for a received invoice by its document ID, including line items, partner information, and prices.

Instructions

Get full detail of one received invoice (přijatá faktura) 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_received_invoice"
  }
}

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 agent knows this is a non-mutating, external-data read. The description adds the useful scope detail that the response includes items, partner and prices, but says nothing about behavior on a non-existent ID, whether attachments/PDF are included, or how large the payload can be.

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 zero filler: verb, resource, lookup key, and returned content in that order. The parenthetical Czech term 'přijatá faktura' earns its place by disambiguating terminology in a multi-language domain.

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 with full schema coverage and no output schema, the description covers purpose, selector, and returned content adequately. Only minor gaps remain, such as error behavior for an invalid ID and whether related artifacts like PDFs are included.

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?

Schema coverage is 100% and the schema already clarifies the single parameter ('Document ID (not the document number)'), doing the heavy lifting. The description only echoes 'by ID' and adds no formatting, range, or sourcing guidance beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Get full detail of one received invoice ... by ID') and enumerates what the detail contains (items, partner, prices), which naturally distinguishes it from the sibling list_received_invoices. It never names an alternative tool explicitly, so the differentiation is implied rather than stated.

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?

Usage is implied: use this when you already have a document ID and need the single record's full detail rather than a list. There is no explicit when-to-use/when-not guidance, no mention of how it relates to list_received_invoices or get_document_pdf, and no note about what to do when the ID is unknown.

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