Skip to main content
Glama

The Doll Scout Home Tools

Build an archive index · Condition-change photos

tds_incident_photo_index
Read-onlyIdempotent

Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set. Condition-change photos. Inspection IDs needing a 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>",
      "requiredInspectionIds": "<requiredInspectionIds>"
    },
    "name": "tds_incident_photo_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordPairsYes
requiredInspectionIdsYes

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description does add one real behavioral fact beyond that — the output separates duplicate IDs and entries absent from the required set — but it never says what happens to malformed or unmatched rows, nor how the results are presented.

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?

Three sentence fragments with no shared subject: the main action, then a domain label, then a noun phrase with no predicate. It is short, but the terseness costs comprehension rather than earning it.

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?

A two-parameter reconciliation tool with no output schema and 0% schema coverage needs the description to explain input encoding and returned categories. It gestures at the categories but says nothing about the encoding, so an agent cannot construct a valid call 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 description coverage is 0%, so the description carries the full burden, and it fails. 'recordPairs' and 'requiredInspectionIds' are opaque 2600-character strings; the description never states the delimiter, line format, or ID syntax. Only the loose hint 'explicit ID and folder pairs' points at the shape of one parameter.

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 sentence names an action (sort ID/folder pairs, separate duplicate IDs and entries missing from the expected set), which is more specific than the title's vague 'Build an archive index'. But the trailing fragments ('Condition-change photos. Inspection IDs needing a record.') are noun phrases with no verb, so the subject domain is guesswork, and nothing distinguishes this from tds_condition_sheet_index or the other *_index siblings.

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 statement, no prerequisite, and no named alternative. 'Condition-change photos' is a topic label, not guidance on when to reach for this tool instead of tds_condition_photo_review or tds_condition_sheet_index.

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.