Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Objects sent to a photo studio

tds_handoff_photo_studio
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Objects sent to a photo studio. Studio check-in identifiers.

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>",
      "studioCheckinIds": "<studioCheckinIds>"
    },
    "name": "tds_handoff_photo_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
studioCheckinIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral fact that the result is a list of units absent at each handoff, but it says nothing about ID input format, how duplicates or unmatched entries are treated, or what a clean match returns.

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?

The operational sentence is correctly front-loaded, but two of the three sentences are filler fragments that consume space without adding meaning. The definition would be stronger trimmed to the first sentence plus a format hint.

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 three-required-parameter comparison tool with no output schema and zero schema descriptions, the description is too thin: input list format and result shape are unaddressed. An agent could call it, but only by guessing at how the ID strings must be encoded.

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 carries the full burden for three required parameters. It names planned, departure and 'arrival' IDs, but the third does not match the schema name studioCheckinIds, and no delimiter, encoding, or length expectation is given despite maxLength hints of 1600/2600 characters.

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 first sentence gives a concrete operation set: match planned/departure/arrival ID lists and report units absent at each handoff, which is enough to separate it from generic list/query siblings. It stops short of differentiating itself from the other tds_handoff_* tools, and the trailing fragments ('Objects sent to a photo studio') add thematic noise rather than precision.

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 when-to-use, when-not-to-use, or prerequisite guidance. Nothing tells an agent when this three-way reconcilation is preferred over the many other handoff siblings, so invocation has to be inferred from the name and the word 'handoff' alone.

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.