Skip to main content
Glama

Storewire Lite demo store

Find datasheets, manuals and other downloads

find_documents
Read-onlyIdempotent

The downloads Trailhead Supply offers for a product model or a brand (manual, care_guide, size_chart, warranty), grouped by model, each file with its type, title, language, version, size and download link (open_url when a browser can show it inline). Narrow by query (a model number, a product's public_id or URL, or words of a title), by brand and by file type. A file hosted by its manufacturer is marked external.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of models, from 1.
typeNoOnly this kind of file.
brandNoA brand name.
limitNoMost files in the answer (default and maximum 20).
queryNoA model number, a product's public_id or page URL, or words of a document title.
localeNoAnswer language: en (default en). Names, labels and URLs follow it.

Output Schema

NameRequiredDescriptionDefault
urlYesThe store's downloads page.
moreYesMore files than this answer holds: ask the next page or narrow the query.
pageYes
totalYesModels matching, across pages.
modelsYes
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
answer_typeNoWhat this answer is, for rendering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive closed-world lookup, so the safety profile needs no restating. The description adds real behavioral context beyond them: results are grouped by model, each file carries type/title/language/version/size, open_url is for inline-viewable files, and manufacturer-hosted files are flagged external.

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?

Front-loaded with what is returned, then how to narrow it, with no filler sentences. The phrasing is dense but each clause carries information; the return-shape detail is the only part that overlaps with the output schema.

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 six optional parameters, full schema coverage, annotations and an output schema, the description supplies everything an agent needs to call it correctly: scope, grouping, narrowing options, limit default/max and the external marker. Only an explicit routing statement versus sibling search/product tools is missing.

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 100%, so every parameter is already documented in the input schema, and the description's query/brand/type/limit notes largely restate those descriptions. Baseline 3 applies; it does not add syntax or format detail beyond the schema.

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?

Names a specific verb+resource (downloads/datasheets, manuals, care guides, size charts, warranty files) and scopes it to a product model or brand. That resource is clearly distinct from the sibling product/cart/search tools, so an agent can pick it without opening the schema.

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?

The opening sentence establishes the context of use (retrieving downloads for a model or brand) and the third sentence tells the agent how to narrow results via query, brand and file type. It does not name an explicit alternative or a when-not condition, so it stops short of a 5.

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.