Skip to main content
Glama

The Doll Scout Home Tools

Build an archive index · Shelf condition photographs

tds_shelf_photo_index
Read-onlyIdempotent

Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set. Shelf condition photographs. Required shelf photo IDs, one per line.

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>",
      "requiredShelfPhotoIds": "<requiredShelfPhotoIds>"
    },
    "name": "tds_shelf_photo_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordPairsYes
requiredShelfPhotoIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare read-only, non-destructive, idempotent, closed-world behavior, and the description adds that duplicate IDs and entries missing from the expected set are separated. However, it does not explain what “separate” means operationally or how results are reported.

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 main operation, with no filler sentences. The fragmented “Shelf condition photographs” line and abrupt final sentence keep it from being maximally clear, but it is appropriately sized.

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 tool with two required string inputs, no output schema, and no parameter descriptions, the description should explain input format and what the returned index looks like. It mentions sorting and separation but leaves the output shape and the meaning of duplicate/missing categories under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It does identify that one input is explicit ID/folder pairs and the other is required shelf photo IDs supplied one per line, but it omits delimiter/line-format specifics that an agent would need for exact input construction.

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 description states an operation on ID/folder pairs (sorting and separating duplicates/missing entries), but it never plainly says it builds an index and does not clearly distinguish the task from sibling index tools. The fragment “Shelf condition photographs” adds domain context without defining the resource or output precisely.

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 guidance, no exclusions, and no explicit alternative such as a different shelf/condition index tool. An agent must infer the intended workflow from the name and description 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.