Skip to main content
Glama
Sign In
idoklad-mcp

idoklad-mcp

by honzsik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get customer payment statistics

get_contact_stats
Read-only

Retrieves invoice payment statistics for a contact, including invoice counts, total invoiced amounts, paid and unpaid invoices, and late payments.

Instructions

How a customer pays: number of invoices, total invoiced, how many are paid, unpaid and were paid after the due date.

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": {
      "contactId": "<contactId>"
    },
    "name": "get_contact_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdYesContact ID (see list_contacts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/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 real value by disclosing what is computed (paid, unpaid, and paid-late counts plus total invoiced), but it says nothing about the time window of the aggregation, currency handling, or whether counting is affected by deleted documents.

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

Conciseness4/5

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

One sentence, front-loaded with the framing clause and then the enumerated metrics; nothing is wasted. It is slightly telegraphic ('How a customer pays' is informal), which keeps it just below the top mark.

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

Completeness3/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 is the only documentation of return values and it does list the main metrics, which is adequate. However, for an aggregation tool the missing scope—over what period and in which currency—is a material gap for correct interpretation of the numbers.

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 description coverage is 100% and the single contactId parameter is documented in the schema, including a pointer to list_contacts. The description adds no syntax or constraint detail beyond that, 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 names the resource (customer payment behavior) and enumerates the concrete metrics returned: invoice count, total invoiced, paid/unpaid counts, and late payments. It does not explicitly differentiate itself from the sibling get_business_stats, which likely offers an aggregate view, so an agent must infer the per-contact vs. business-wide distinction.

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: needing payment behavior for a single contact. There is no statement of when to prefer this over get_business_stats or the various list_* invoice tools, and no prerequisites or exclusions are given. The schema's 'see list_contacts' hint helps an agent obtain the ID but is not usage guidance.

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