Skip to main content
Glama

search_works

Read-onlyIdempotent

Core discovery tool. Use when the buyer asks for examples such as 'who has made a 6061-T6 medical endoscope housing to ±0.01 mm' or wants factories with experience in an industry. Returns work title, material, process, industry, tolerance, images and canonical source URL, plus supplier context. Results are newest-first. Works without English/published projection are excluded.

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": "search_works"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 20.
regionNoSupplier province or city substring.
processNoCapability/process id, e.g. cnc-machining/03.
industryNoIndustry cluster or detail substring, e.g. aerospace or medical.
materialNoSingle material substring; alias for materials.
materialsNoMaterial substrings; any match is accepted.
supplier_idNoRestrict to one supplier.
tolerance_max_mmNoOnly return works with declared tolerance at or below this value in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds useful behavior: results are newest-first, records lacking English/published projection are excluded, and each result carries supplier context plus a canonical source URL. Ordering and filtering semantics are exactly the kind of context annotations cannot convey.

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 the core purpose and the highest-value use case in the first two sentences, followed by return shape and ordering. The return-field enumeration is slightly list-like but each item is informative and the whole thing stays short.

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 8 optional parameters, no enums and no output schema, the description supplies the missing pieces an agent needs: what comes back, how results are ordered, and which records are filtered out. Only a note on default result count/pagination interaction with limit is left to the schema.

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 coverage is 100%, so every parameter is already documented, which sets the baseline at 3. The worked example ('6061-T6 medical endoscope housing to ±0.01 mm') implicitly demonstrates how material, industry and tolerance_max_mm combine in one query, adding modest meaning beyond the schema but no explicit parameter guidance.

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 description gives a specific verb and resource ('Core discovery tool' for finding works, with concrete examples of material/process/industry/tolerance queries) and enumerates the returned fields. It is clear what the tool returns and roughly how it differs from get_work/search_suppliers by emphasizing example-based discovery plus 'supplier context', though it never names a sibling explicitly.

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 states a clear triggering condition ('Use when the buyer asks for examples such as...' or 'wants factories with experience in an industry'), which maps directly onto real query patterns. It also gives an exclusion rule (unpublished/non-English works are dropped), but offers no explicit when-not or alternative-tool 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.

Resources