Skip to main content
Glama
Sign In
idoklad-mcp

idoklad-mcp

by honzsik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get proforma invoice

get_proforma_invoice
Read-only

Retrieve full details of a proforma invoice by its document ID, including line items, partner information, and prices.

Instructions

Get full detail of one proforma invoice (zálohová 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_proforma_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 safety is covered. The description adds value by disclosing what the payload contains (items, partner, prices), which matters since there is no output schema, but says nothing about error behavior for missing IDs or any access constraints.

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 sentence that front-loads the verb and resource and then lists the returned sections. No filler, no restatement of the title, nothing to trim.

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 annotations, this is nearly complete; the content preview substitutes reasonably for the absent output schema. Only failure modes and how to obtain a valid ID are missing.

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 states 'Document ID (not the document number)', which is the key disambiguation. The description only repeats 'by ID' and adds no format, type, or sourcing guidance beyond the 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?

Specific verb + resource: 'Get full detail of one proforma invoice ... by ID', with the Czech alias (zálohová faktura) and a preview of returned content. The singular 'one ... by ID' implicitly separates it from list_proforma_invoices, but no sibling is named, so differentiation is left to inference.

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 only implied: fetch when you need full detail for a single document and you already have the ID. There is no explicit when-to-use, no pointer to list_proforma_invoices for discovery of IDs, and no stated behavior 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