Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

Receivables

finance_receivables
Read-only

Retrieve open and overdue invoices with totals to track outstanding receivables. Optionally filter to show only overdue invoices for focused collections follow-up.

Instructions

Open and overdue invoices, with totals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finance_receivables"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyOverdueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds one genuine behavioral fact beyond the annotations — that totals accompany the invoice list — but says nothing about pagination, ordering, currency, or what 'open' versus 'overdue' mean operationally.

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?

Six words, front-loaded, with no filler or redundancy. Its economy is a virtue even though the content is thin.

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 read-only tool with one optional parameter and no output schema, the essentials are nearly there, but the description never clarifies the return payload (what totals mean, per-invoice vs aggregate) or the effect of the sole parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single onlyOverdue parameter, so the description must compensate. It implies the default result includes both open and overdue invoices, but never explains what onlyOverdue does or how the result changes when it is true, leaving the one parameter semantically undefined.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (invoices) and the subset returned (open and overdue), plus that totals are included. But it is a bare noun phrase with no verb ('list', 'get', 'summarize'), and it does not distinguish this from any sibling, so an agent knows roughly what data it touches but not what action it performs.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus another tool, no prerequisite or auth context, and no exclusions. The only implicit guidance is that the tool concerns receivables, which the agent gets from the name alone.

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