Skip to main content
Glama

The Doll Scout Home Tools

Check preflight readiness · Archive cover checks

tds_preflight_archive_cover
Read-onlyIdempotent

Read explicit ready, pending and blocked entries and identify required items missing from the checklist. Archive cover checks. Required case cover checks.

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": {
      "statusRows": "<statusRows>",
      "requiredArchiveCoverIds": "<requiredArchiveCoverIds>"
    },
    "name": "tds_preflight_archive_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusRowsYes
requiredArchiveCoverIdsYes

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 establish that this is a safe, read-only, idempotent, closed-world operation. The description adds that it reads explicit ready/pending/blocked entries and identifies missing required items, which is useful behavioral context. However, it does not describe the return shape, how statuses are interpreted, or what happens with malformed entries, leaving some behavioral gaps beyond the annotations.

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 useful action statement is front-loaded, but the following fragments 'Archive cover checks' and 'Required case cover checks' are redundant and add little value. The description is short, but it wastes part of its limited space on restating the title rather than clarifying input format or output behavior.

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?

This is a low-complexity read-only tool with two required string parameters and no output schema, so the description should carry more of the burden. It explains the high-level comparison but omits both input encoding details and what the tool returns, which are essential for calling it correctly.

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 coverage is 0%, so the description must compensate for both parameters being undocumented strings. It hints that statusRows contains ready/pending/blocked entries and that requiredArchiveCoverIds represents required items, but it does not explain the expected string format, delimiters, encoding, or how the two inputs relate. The maxLength constraints and serialization expectations are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific action: read ready/pending/blocked entries and identify required items missing from the checklist. The phrase 'Archive cover checks' names the resource, though the trailing fragment 'Required case cover checks' is redundant and vague. It is clear enough to distinguish from unrelated siblings, but it does not explicitly contrast with the many other preflight_* tools.

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?

The description does not say when to use this tool, when not to use it, or which sibling tools it replaces. It implies usage as a preflight readiness check but offers no explicit context, prerequisites, or alternative routing.

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.