Skip to main content
Glama

category_check

Read-onlyIdempotent

How many Chinese CES brands sell a product, split by overseas stage and home city, with total companion-app installs.

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": {
      "product": "<product>"
    },
    "name": "category_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct words, for example "power station"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral content: this is an aggregation whose results are partitioned by overseas stage and home city and include a summed installs metric — valuable since no output schema exists.

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?

One front-loaded sentence that carries the scope, the split dimensions, and the extra metric with no filler. It is a sentence fragment rather than a full statement, but nothing is redundant.

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?

For a single-parameter read-only tool with no output schema, the description covers what is computed and the dimensions of the return value, which is close to sufficient. It leaves undefined how 'overseas stage' is bucketed, what 'CES brands' scope means, and what units the install totals use.

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?

There is a single required parameter with 100% schema description coverage, and the schema already explains it as product words with an example ('power station'). The description only implies that the same product term drives the counting, adding no semantics beyond the schema, so the high-coverage baseline of 3 applies.

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 names a specific subject (Chinese CES brands that sell a given product) and the exact breakdowns produced (overseas stage, home city, total companion-app installs), so an agent can tell it is a counting/aggregation query. It lacks an explicit verb ('count', 'return') and the tool name 'category_check' does not echo the described behavior, so the match takes a small inference.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the sibling tools get_brand and search_brands, and no statement of preconditions or exclusions. The agent must infer that this is the aggregate/statistics option while the siblings are entity lookups.

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