Skip to main content
Glama

lots_reconcile

Read-onlyIdempotent

식별자 정합 — 여러 체계·주체의 품목 코드/로트 코드가 같은 품목·같은 로트를 가리키는지(추론 없음·가격 없음)

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": {
      "identifiers": "<identifiers>"
    },
    "name": "lots_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifiersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior. The description adds useful scope constraints ('no inference, no pricing'), but does not explain matching semantics, ambiguity handling, or what a reconciliation result contains.

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?

It is a single front-loaded sentence with the core purpose first and scope exclusions in a parenthetical. There is little waste, though the em-dash phrasing is slightly compressed.

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 reconciliation tool taking a nested identifiers array, the definition is too terse: it does not describe result semantics, matching behavior, ambiguity handling, or limits such as the maximum number of identifiers. Annotations cover safety, but without an output schema the description should carry more behavioral context.

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?

The description broadly indicates that identifiers span multiple schemes/parties and item/lot codes, but it does not explain the required structure, the role of jurisdiction, or how kind/scheme/party/code fields are used. With schema description coverage reported at 0%, the description does not compensate for the parameter-level gap.

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 operation: identifier reconciliation across multiple schemes/parties, checking whether item codes or lot codes refer to the same item or lot. It is clear enough to distinguish from pricing and inference tools, though it does not explicitly name a sibling alternative.

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 implied by the stated purpose — use it when checking code equivalence — and the parenthetical exclusions ('no inference, no pricing') clarify scope. However, it gives no explicit when-to-use/when-not guidance or named alternatives.

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