Skip to main content
Glama

get_store_order_reconciliation

Read-onlyIdempotent

Read recorded payment and refund reconciliation for an order. Amounts are minor units in the order currency. Timestamps are Unix milliseconds.

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": {
      "id": "<id>"
    },
    "name": "get_store_order_reconciliation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already fully cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's contribution is data semantics: amounts are in minor units of the order currency and timestamps are Unix milliseconds. These are real, non-obvious facts that prevent unit misinterpretation. It does not disclose pagination behavior despite the offset parameter, keeping it below 5.

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?

Three short sentences, front-loaded with the what, then two compact data-format rules. No filler, no redundancy.

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 bears more burden. It establishes units and timestamp encoding but does not say what the response contains (payment vs refund entries, totals, statuses) or how offset affects the result. Adequate for identification, thin for correct invocation of the paging 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%, so the description must carry the meaning. It never explains `id` explicitly (only implied by 'for an order') and says nothing at all about `offset` — that it is a pagination cursor, how results are paged, or what the 100000 maximum implies. The unit/format notes added are about returned values, not parameters.

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?

Specific verb+resource: 'Read recorded payment and refund reconciliation for an order.' The scope ('recorded' reconciliation for a single order) is distinct from get_store_order, which likely returns the order itself rather than its reconciliation records. It stops short of naming a sibling to contrast with, so 4 rather than 5.

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 when-to-use, when-not-to-use, or alternative routing guidance. An agent must infer from the name/purpose that this is used after an order exists and only when reconciliation data is wanted rather than the order itself. Implied usage only.

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.

Resources