Skip to main content
Glama

The Doll Scout Home Tools

Build an archive index · Loan record archive

tds_loan_archive_index
Read-onlyIdempotent

Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set. Loan record archive. Loan references to reconcile.

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>",
      "requiredLoanIds": "<requiredLoanIds>"
    },
    "name": "tds_loan_archive_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordPairsYes
requiredLoanIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 safety and repeatability are covered structurally. The description usefully adds that the operation partitions input into duplicates and entries missing from the expected set, but it never says whether the result is a report, a count, or filtered lists, nor how the inputs are delimited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and the operative sentence is front-loaded, which is good, but the following two sentence fragments ("Loan record archive." and "Loan references to reconcile.") are near-duplicative and add no information that earns their space.

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?

There is no output schema, so the description must explain what is returned, and it does not — the agent cannot tell the shape of the "separated" result. Combined with the entirely undocumented input string formats, the definition is under-specified for a two-parameter reconciliation tool.

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% and both required parameters are opaque strings with maxLength 2600, so the description carries the full burden. "Explicit ID and folder pairs" partially maps to recordPairs and "the expected set" maps to requiredLoanIds, but no format is given — no separator, line-per-pair convention, or whether IDs are numeric, prefixed, or case-sensitive — which is exactly what an agent needs for a free-text blob 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 description names an operation ("Sort explicit ID and folder pairs and separate duplicate IDs and entries missing from the expected set") that is more specific than the title, but "sort" is ambiguous — it is unclear whether it orders, groups, or classifies — and the trailing fragments "Loan record archive. Loan references to reconcile." do not pin down what an archive index actually is. Nothing in the text distinguishes it from the many sibling *_index tools (tds_condition_sheet_index, tds_receipt_folder_index, etc.).

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 named alternative among the siblings for reconciling loan references. Usage is only weakly implied by the phrase "Loan references to reconcile," leaving the agent to guess the trigger conditions.

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.