Skip to main content
Glama

search_exporters

Read-onlyIdempotent

Search 993 Chinese medical exporters from the Canton Fair by name, city or province.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 20, max 50
queryYesName, city or province words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful dataset context (a fixed corpus of 993 records drawn from the Canton Fair), but it does not disclose matching semantics—substring, fuzzy, or exact—which is the main behavioral question for a search tool.

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?

A single tight sentence with the scope and searchable fields front-loaded and no filler. Every element—corpus size, domain, source, and queryable dimensions—earns its place.

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

Completeness3/5

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

There is no output schema, and the description says nothing about what an exporter record contains or how results are ordered, which is a real gap for a discovery tool. For a simple two-parameter read-only search it is otherwise adequate, so this is a moderate rather than severe shortfall.

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%, with both `query` and `limit` documented inline including the default of 20 and cap of 50. The description's 'by name, city or province' merely restates the schema's 'Name, city or province words' rather than adding detail on matching or multi-word behavior, so the baseline 3 applies.

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?

The description states a specific verb (Search) and a precisely bounded resource (993 Chinese medical exporters from the Canton Fair), plus the three searchable fields. Nothing about the tool's function is left ambiguous, and the sibling tools (latest_clearances, review_time) belong to unrelated domains so no differentiation is owed.

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

Usage Guidelines3/5

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

Usage is implied by the search semantics but never stated: there is no 'when to use this' framing, no mention of what happens when a query returns nothing, and no suggestion to narrow by city vs. province. Given the unrelated siblings, explicit alternatives are unnecessary, but the description still leaves the agent to infer intent.

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