Skip to main content
Glama

Consignment Remittance

bpj_consignment_remittance
Read-onlyIdempotent

Reconcile consigned units available, returned and still held to the remittance due on sold units.

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": {
      "consigned": "<consigned>",
      "returned": "<returned>",
      "remain": "<remain>",
      "settlement": "<settlement>"
    },
    "name": "bpj_consignment_remittance"
  }
}

Input Schema

NameRequiredDescriptionDefault
remainYes
returnedYes
consignedYes
settlementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds almost no behavioral context beyond that: it does not explain the calculation, validation rules, or what the reconciliation result represents.

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?

The definition is a single front-loaded sentence with no filler. It is concise, though its density leaves important operational details unstated.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter calculation tool with no output schema, the description is too thin. It does not state the computation performed or the expected return value, leaving an agent to infer the reconciliation logic.

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 0%, so the description must carry parameter meaning. It maps the four inputs to consigned, returned, held, and remittance concepts, but it does not clarify the formula, units, or how 'remain' relates arithmetically to the other inputs.

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 states a specific reconciliation action over consigned units, returned units, held units, and remittance. It is clear enough to identify the tool's domain, but it does not differentiate from any sibling or clarify the exact reconciliation formula.

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 explicit guidance on when to use this tool, when not to use it, or what alternatives exist. The intended use is only implied by the word 'Reconcile' and the parameter names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.