The Doll Scout · Collecting Tools

search_collection_series

Read-onlyIdempotent

Search the source-linked SMISKI and Sonny Angel catalog by series or figure name. Returns candidate series IDs, verified named styles, source URLs and per-series check dates directly. Catalog coverage can omit secret or discontinued figures; choose the exact series before comparing a collection.

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": {
      "query": "<query>"
    },
    "name": "search_collection_series"
  }
}

Input Schema

Name	Required	Description	Default
`brand`	No
`limit`	No
`query`	Yes
`language`	No	Interface language; some browser-only tools are available only in EN/DE.	en

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-open-world), so the bar is lower, and the description still adds real value: it discloses what is returned (candidate series IDs, verified named styles, source URLs, per-series check dates) and an honest coverage limitation around secret/discontinued figures. It does not describe result ordering or how partial matches are ranked.

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

Conciseness5/5

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

Three sentences, front-loaded with the core action and payload, followed by the caveat and the workflow guidance. No redundant restatement of the tool name and no filler.

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?

With no output schema, the description carries return-value burden and does so adequately by listing the returned fields. The remaining gap is behavioral detail on limit and brand defaults, which is minor for a read-only search tool with strong annotations.

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 only 25% — only 'language' is documented — so the description must compensate. It explains the query key (series or figure name) and implies the brand split via 'SMISKI and Sonny Angel', but says nothing about the limit cap of 10 or how brand filtering interacts with a free-text query.

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

Purpose5/5

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

States a specific verb (Search) plus the exact resource (source-linked SMISKI and Sonny Angel catalog) and the matching keys (series or figure name). This clearly separates it from the sibling set of probability, checklist and comparison tools, which do not do catalog lookup at all.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit usage context — 'choose the exact series before comparing a collection' — which tells the agent where this fits in a workflow, and warns that coverage can omit secret or discontinued figures. It stops short of naming an alternative tool or a when-not condition, so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Doll Scout · Collecting Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?