Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Loaned prints

tds_handoff_lent_art
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Loaned prints. Arrival IDs for returned prints.

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": {
      "plannedIds": "<plannedIds>",
      "departureIds": "<departureIds>",
      "returnedArtworkIds": "<returnedArtworkIds>"
    },
    "name": "tds_handoff_lent_art"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
returnedArtworkIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds that the result is a report of units absent at each handoff, which is useful output context, but it does not say how the report is shaped or whether mismatched/extra IDs are also surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the three sentences are sentence fragments with no connective logic, and 'Loaned prints' is a title echo that conveys nothing actionable. The core operation is not cleanly front-loaded before the fragmentary modifiers.

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?

Three required parameters at 0% schema coverage with no output schema, plus a comparison/reconciliation result that agents cannot predict, demand more explanation than four short clauses. An agent could not reliably construct the ID inputs or interpret the missing-units report from this definition 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 coverage is 0%, so the description must carry all parameter meaning, and it only partially does: it maps 'planned' and 'departure' to their params and vaguely links 'arrival IDs for returned prints' to returnedArtworkIds. The input format is unclear — all three are strings with large maxLengths, suggesting delimited ID lists, but neither schema nor description says so.

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 first clause states a concrete operation: matching planned, departure and arrival IDs and reporting units absent at each handoff. However, it is fragmented ('Loaned prints.', 'Arrival IDs for returned prints.') and never names the sibling it differs from among the many tds_handoff_* tools, so the scope is only implied.

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 choose this reconciliation tool over the other handoff tools (binders, props, cartons, totes). The only routing hint is the dangling phrase 'Loaned prints', which gestures at a domain but does not set a condition for use.

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.