Skip to main content
Glama

The Doll Scout Home Tools

Build an archive index · Product guide folders

tds_manual_index
Read-onlyIdempotent

Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set. Product guide folders. Models with expected manuals, 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>",
      "requiredManualIds": "<requiredManualIds>"
    },
    "name": "tds_manual_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordPairsYes
requiredManualIdsYes

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed operation. The description adds some behavioral context by mentioning duplicate-ID separation and detection of entries missing from the expected set, but it does not explain what that separation looks like or what the caller receives.

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 description is short but poorly structured, consisting of fragmentary sentences with unclear referents. The core operation is not front-loaded, and the trailing fragments do not earn their place by clarifying the inputs.

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?

With no output schema and two required string parameters at 0% schema coverage, the description should explain the input format and what the index/result contains. It leaves both the line-based input syntax and the output shape largely unexplained.

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 must carry parameter meaning. It only vaguely maps recordPairs to 'explicit ID and folder pairs' and requiredManualIds to 'models with expected manuals, one per line'; the required line format, delimiters, and duplicate-handling semantics remain unspecified.

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—sorting ID/folder pairs and separating duplicates and missing entries—but it is fragmented and never clearly says what the tool ultimately produces. It gives no differentiation from siblings such as tds_loan_archive_index or tds_receipt_folder_index.

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 guidance, no prerequisites, and no indication of when another archive-index sibling would be more appropriate. The fragments about product guide folders and models with expected manuals imply a domain but not selection criteria.

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.