Skip to main content
Glama

The Doll Scout Home Tools

Check preflight readiness · Photo view checklist

tds_preflight_photo_views
Read-onlyIdempotent

Read explicit ready, pending and blocked entries and identify required items missing from the checklist. Photo view checklist. Required photo view identifiers.

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>",
      "requiredPhotoViewIds": "<requiredPhotoViewIds>"
    },
    "name": "tds_preflight_photo_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusRowsYes
requiredPhotoViewIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 is covered. Beyond that, the description adds only the notion of comparing supplied statuses against a required list; it says nothing about how the comparison is computed, whether the two inputs must be in a particular serialized form, or what the resulting verdict looks like. For a validator whose entire value is the outcome it produces, that is a real gap.

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 first sentence is compact and front-loaded with the actual operation. The two trailing fragments are wasteful — they repeat the title and the parameter names without conveying new information, reading like leftover labels rather than usable guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Placeholder justification to be replaced with a real assessment of completeness relative to tool complexity.

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 parameters are bare strings with maxLength 2600, so neither shape nor format is documented anywhere. The trailing phrases 'Photo view checklist' and 'Required photo view identifiers' gesture at the two inputs but give no syntax, expected encoding, or element structure. With the schema silent, the description needed to carry this load and does not.

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 opening clause does state a recognizable operation — read ready/pending/blocked entries and flag required items missing from that checklist — which is more than a restatement of the name. However, the follow-on fragments 'Photo view checklist' and 'Required photo view identifiers' merely echo the title and parameter names instead of narrowing scope. With many tds_preflight_* siblings, nothing here distinguishes this checklist from archive_cover, shelf_labels, or the other preflight checks.

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, when-not-to-use, or prerequisite guidance. The description never says this is the gating step before a photo shoot, or how it relates to the other preflight tools that appear as siblings. An agent must infer invocation timing entirely from the name.

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.