Skip to main content
Glama

The Doll Scout Home Tools

Build an archive index · Incoming object folders

tds_incoming_item_index
Read-onlyIdempotent

Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set. Incoming object folders. Expected intake 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>",
      "requiredIntakeIds": "<requiredIntakeIds>"
    },
    "name": "tds_incoming_item_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordPairsYes
requiredIntakeIdsYes

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral content by naming the output categories it separates (duplicate IDs, entries missing from the expected set), which is context the annotations do not supply. It stops short of saying whether the result is one combined listing, grouped sections, or counts, and gives no limits despite the 2600-character input caps.

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 definition is short and front-loads the operation before the parameter hints, with no filler sentences. The weakness is structural rather than verbosity: 'Incoming object folders.' is an orphan fragment with no verb, and the parameter hints are appended as unlabeled fragments, so the reader has to reconstruct which clause describes which parameter.

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 2 required parameters at 0% schema coverage and no output schema, the description needs to explain the input pair syntax and the shape of the returned separation, and it does neither fully. The one-per-line direction for requiredIntakeIds is helpful but recordPairs has no format guidance, and nothing says what the agent gets back. For a two-list reconciliation tool this leaves the callable contract 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% and both parameters are bare strings, so the description carries the burden of explaining them. It does partly compensate: 'explicit ID and folder pairs' tells the agent recordPairs contains ID-to-folder pairings and 'one per line' gives the line-oriented format for requiredIntakeIds. It omits the delimiter or syntax separating an ID from its folder within a pair, and never mentions the maxLength or that both lists are capped.

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 conveys the operation as sorting explicit ID/folder pairs and separating duplicate IDs and entries missing from the expected set, which is more specific than the title alone. However, 'Sort' is a vague verb and the fragment 'Incoming object folders' reads like an unexplained label, so the agent must infer that this is a reconciliation/index-build step rather than a simple sorter. The result is understandable but not crisp.

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 use this tool, no prerequisites, and no exclusion of alternatives. Siblings such as tds_loan_archive_index, tds_condition_sheet_index, and tds_receipt_folder_index appear to be directly adjacent use cases, yet the description gives no condition to choose between them. The agent must guess from the name and parameter names 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.