Skip to main content
Glama
Sign In

materials

by com.spacemushroom
OverviewDiscussionsAdmin

Search space products by description

search_products
Read-onlyIdempotent

Ranked full-text search over everything written about the products: names and aliases, summaries, specs, features, parts, materials, finishes, standards and organizations. Use it when you have a description rather than exact filters ("ablative heat shield on a Mars rover", "regeneratively cooled engine", "thermal blankets for CHEOPS"); use find_products when you can name a kind, size, maker or material. Returns the best matches first with a short snippet of the matching text and the page; open one with get_product. An empty answer means no catalogued text matches those words.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products, 1 to 30 (default 8)
queryYesWords or a short phrase; quotes and minus work (web-search style)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: results are ranked best-first, each carries a snippet and page reference, and an empty answer means no catalogued text matched. It does not discuss pagination or ranking internals, which keeps it just short of a 5.

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 capability, then the routing rule, then the return contract. Every clause carries information an agent needs; no filler or restatement of the title.

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

Completeness5/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 takes on the burden of describing returns and does so: ranked matches, snippet, page, and the follow-up call to get_product. Combined with the empty-result semantics, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, including the web-search-style quoting and minus syntax. The description still adds value by demonstrating the intended query shape with realistic multi-word phrases, which clarifies what 'query' should look like better than the schema's abstract note.

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 and resource ('Ranked full-text search over everything written about the products') and enumerates the searchable fields, so the agent knows exactly what corpus is covered. It also explicitly contrasts itself with the sibling find_products, making the two tools distinguishable without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('when you have a description rather than exact filters') with three concrete example queries, plus the inverse rule routing to find_products when a kind, size, maker or material is known. It even explains the empty-result case, leaving nothing to inference.

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

All materials toolsInspect
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