Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

Get business statistics

get_business_stats
Read-only

Retrieves business overview reports from iDoklad, including revenue by period, year comparison, overdue aging, VAT, VAT registration limit, and document counts.

Instructions

Business overview calculated by iDoklad. All amounts are in the company's home currency (usually CZK). Reports:

  • revenue_by_period: issued (income) and received (costs) invoice totals per month, quarter or year, with paid/unpaid split.

  • year_comparison: this year's totals against last year's.

  • overdue_aging: overdue amounts by age (1–30, 31–60, 61–90, 90+ days), for receivables (customers owe you) and payables (you owe suppliers).

  • vat: VAT on output and input for the current and previous VAT period (VAT payers).

  • vat_registration_limit: this calendar year's sales against the CZ VAT registration limit (for companies not yet registered for VAT).

  • document_counts: how many invoices, contacts and other documents the company has.

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": {
      "report": "<report>"
    },
    "name": "get_business_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoFor revenue_by_period and vat (vat: month or quarter only).month
reportYes
periodsNoFor revenue_by_period: how many periods back, including the current one. Default 12 months, 4 quarters or 3 years.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/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 genuinely useful context: all amounts are in the home currency, values are pre-calculated by iDoklad, and two reports are conditional on VAT registration status. It does not mention data freshness or whether figures include draft/unpaid documents beyond the paid/unpaid split.

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?

The overview sentence with the currency caveat is front-loaded, followed by a tight bulleted list where each bullet maps to one enum value. No sentence is redundant or repeated from structured fields.

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, the description carries the burden of telling the agent what comes back, and the per-report bullets do that at the level of contents and splits. It stops short of describing the returned field structure or the default date window for year_comparison and overdue_aging.

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 67%, and the description compensates by explaining what each report enum value returns and how period applies to revenue_by_period and vat (month or quarter only). The 'periods' lookback parameter is left entirely to the schema, which is the main remaining gap.

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 ('business overview calculated by iDoklad') and then enumerates the six report values with what each contains, which makes the boundary against siblings like get_contact_stats and get_top_partners clear 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?

Each report value is described well enough that an agent can pick the right one for a question (e.g. overdue_aging for receivables/payables aging, vat_registration_limit only for non-registered companies). It never names an alternative tool or states when not to use this one, so explicit routing guidance is absent.

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