Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

Get top customers or debtors

get_top_partners
Read-only

Rank customers by total invoiced amount or debtors by unpaid amount to reveal who drives revenue or owes money, using home-currency amounts.

Instructions

Biggest customers by total invoiced, or biggest debtors by unpaid amount (who owes you the most). Amounts in home currency.

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": {
      "kind": "<kind>"
    },
    "name": "get_top_partners"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a read-only, open-world call, so safety is covered. The description adds one genuinely useful behavioral fact — all amounts are normalized to home currency — which an agent could not infer from structured fields. It does not disclose ordering, aggregation window (no date parameter exists), or whether debtors means overdue-only.

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 with no filler; the primary metric distinction is front-loaded and the currency note trails as a qualifier. Nothing could be removed without losing information.

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?

For a simple two-parameter read tool this is close to adequate, but with no output schema the description should say what comes back (entity, amount, ranking order) and whether the figures cover all time. Those gaps matter for an agent deciding how to present or trust the results.

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 0%, so the description carries the burden. It successfully maps the 'kind' enum values to their metrics, which is real added meaning. However, 'count' is never explained in the description, and the reader must infer that it caps the number of returned entities and defaults to 10.

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 and the two concrete metrics: 'biggest customers by total invoiced' and 'biggest debtors by unpaid amount', with a clarifying gloss '(who owes you the most)'. This tells an agent precisely what the tool computes. It stops short of stating the output is a ranked list, which is why it is a 4 rather than a 5.

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?

Guidance is limited to choosing between the two modes, and that choice is embedded in the metric definitions rather than framed explicitly. There is no statement about when to prefer this over siblings such as get_business_stats or get_contact_stats, and no prerequisites or exclusions.

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