Skip to main content
Glama

search_brands

Read-onlyIdempotent

Search 1,546 Chinese AI, robot and gadget brands from CES 2026 and 2027 by product or name. Returns overseas stage, city, hero products and page URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 20, max 50
queryYesProduct or brand words, for example "robot vacuum" or "anker"
stageNoOptional overseas stage filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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-destructive, closed world), so the description's added value is the return shape: overseas stage, city, hero products and page URL. That is meaningful behavioral context, especially since no output schema exists. It does not say how results are ranked or ordered, which keeps it below 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?

Two sentences, zero filler, with the corpus scope and search modes front-loaded before the return fields. Every clause carries information an agent can act on.

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?

For a simple three-parameter read-only search, the description plus annotations and full schema coverage tell the agent nearly everything needed to call it. The only gap is ordering/ranking behavior of results, a minor omission rather than a blocker.

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 all three parameters (query, stage, limit) are already documented with examples and ranges. The description's phrase 'by product or name' loosely maps to the query parameter but adds no new constraint or format detail. Baseline 3 is correct when the schema does the heavy lifting.

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?

Specific verb and resource with real scope detail: 'Search 1,546 Chinese AI, robot and gadget brands from CES 2026 and 2027 by product or name.' An agent immediately knows this is a keyword search over a brand corpus, which differentiates it from a single-record lookup like get_brand. It stops short of explicitly naming the sibling alternative, so a 4 rather than a 5.

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 'by product or name', which suggests the two query styles. There is no explicit when-to-use versus when-to-use-another-tool guidance, and no discussion of prerequisites or coverage limits. Adequate but leaves routing inference to the agent.

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