Skip to main content
Glama

The Doll Scout Home Tools

Build an archive index · Transport paperwork

tds_transport_paperwork_index
Read-onlyIdempotent

Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set. Transport paperwork. Shipment IDs needing an archived record.

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": {
      "recordPairs": "<recordPairs>",
      "requiredShipmentIds": "<requiredShipmentIds>"
    },
    "name": "tds_transport_paperwork_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordPairsYes
requiredShipmentIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety behavior is covered. The description usefully adds that duplicate IDs and entries missing from the expected set are separated, but it does not explain the output structure or comparison behavior.

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 description is short and front-loads the operation, with no wasted explanation. The fragmentary domain sentences are terse rather than verbose, though they contribute little structure.

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 two-input tool with no output schema and 0% parameter description coverage, the definition should explain how to encode the inputs and what the separated results look like. It does not, leaving the agent without enough detail to invoke the tool correctly from the description alone.

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 two required string parameters. The description hints that recordPairs are ID/folder pairs and requiredShipmentIds is the expected set, but it gives no formatting, delimiter, ordering, or length guidance, so it only weakly compensates for the missing schema documentation.

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 opening sentence gives a concrete operation — sorting explicit ID/folder pairs and separating duplicate IDs and missing entries — and ties it to transport paperwork and archived shipment records. It does not explicitly name sibling alternatives, but the broad purpose is clear to an agent.

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 or when-not-to-use guidance and no named alternative among siblings. The phrase 'Shipment IDs needing an archived record' adds domain context but not a real decision rule.

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.