Skip to main content
Glama

get_brand

Read-onlyIdempotent

Facts for one brand by id (from search_brands): overseas stage, web rank, US search volume, Google Play installs of its companion app, and 30-day news count, each with its date.

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": {
      "id": "<id>"
    },
    "name": "get_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBrand id, for example "ecovacs-robotics"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered and the description need not repeat it. What it adds beyond annotations is the return payload shape (web rank, search volume, installs, news count) plus the fact that each value carries its own date, which is useful staleness context. It stops short of describing failure behavior or data freshness limits.

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?

One front-loaded sentence that puts the subject and lookup key first, then the payload list. Nothing is redundant with the annotations and every clause earns its place.

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?

There is no output schema, so the description must carry return content, and it enumerates the five fact families with their date stamping. That is sufficient to call and use the tool; only edge cases such as unknown ids or missing metrics are left unspecified, which is a minor gap for a single-parameter read.

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% and even supplies an example id, so the schema does most of the work. The description still adds meaning the schema lacks: the id must come from search_brands, which tells the agent where valid identifiers originate and prevents ad-hoc id construction.

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 ("Facts for one brand by id") and immediately enumerates the fact types returned, so the agent knows exactly what it gets and how it differs from search_brands, which returns a list. No sibling ambiguity remains.

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?

The parenthetical "(from search_brands)" establishes the workflow prerequisite: obtain the id from search_brands before calling this. It gives clear usage context but does not state when not to use it (e.g., bulk retrieval) or what happens with an invalid id.

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