Skip to main content
Glama
Sign In
idoklad-mcp

idoklad-mcp

by honzsik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Call iDoklad API

idoklad_api_request
Read-only

Call any iDoklad API v3 GET endpoint directly to retrieve account data; find the endpoint with search_api_docs, then pass a relative path and query parameters.

Instructions

Call any iDoklad API v3 endpoint directly (find it with search_api_docs first). Path is relative, e.g. 'BankStatements'. List endpoints accept filter, sort, page and pagesize query parameters; filter syntax: (FieldopvalueandFieldopvalue) with ops eq, !eq, lt, lte, gt, gte, ct, !ct. Read-only mode: only GET is allowed.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "idoklad_api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for POST, PUT, PATCH.
pathYesEndpoint path after /v3/, e.g. 'IssuedInvoices/123'.
queryNo
methodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is largely covered; the description largely restates the read-only constraint ('only GET is allowed') rather than adding to it. It does not warn that the open-world endpoint surface may vary in shape or error semantics per resource, which would have been genuine added context.

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?

Three tight sentences: purpose first, then the discovery precondition, then the wire syntax details. Every clause carries operative information and the most consequential constraint (read-only) is placed last as a guardrail.

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?

With no output schema and an open-world generic proxy, the key unknowns an agent needs are the path form, allowed method, and query syntax, all of which are supplied. The remaining gap is that it does not describe the response payload or error behavior returned by arbitrary endpoints, though for a generic passthrough that is a moderate omission.

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?

Schema coverage is only 50%, so the description has to compensate, and it does: it documents the list-endpoint query parameters (filter, sort, page, pagesize) plus a full filter operator grammar (eq, !eq, lt, lte, gt, gte, ct, !ct). That is meaningfully more than the schema provides for the undescribed 'query' parameter, though 'body' and the method restriction remain schema-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Call any iDoklad API v3 endpoint directly'. It distinguishes this generic escape hatch from typed sibling helpers by pointing to search_api_docs for endpoint discovery, so an agent can tell what this tool is for without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete discovery guidance ('find it with search_api_docs first') and a path-format example ('BankStatements'), so the agent knows the preceding step and the path shape. It stops short of saying when to prefer a dedicated sibling like list_issued_invoices over this generic call, which is the main missing selection rule.

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