Skip to main content
Glama

get_brand_details

Read-onlyIdempotent

Get a brand profile: description, official website, company, aliases, rating, categories and the product models listed under the brand. Identify the brand with brand_id (from search_brands), slug, or brand_name.

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

Input Schema

NameRequiredDescriptionDefault
slugNoBrand slug in the form {id}-{text}, as used in the source URL.
brand_idNoBrand id returned by search_brands.
languageNoOptional language code.
brand_nameNoBrand name, used when no id or slug is known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds that the result is a profile with a fixed field set, but says nothing about behavior on an unknown brand (error vs. empty), partial-match fallback for brand_name, or whether the product models list is truncated.

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?

Two sentences, front-loaded with the return contents followed by the identification options, with no filler. The field enumeration is long but justified because there is no output schema.

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 no output schema, the description carries the burden of describing the return value and does so concretely. It is slightly incomplete on edge cases for a lookup tool (unknown brand, ambiguous name, non-existent slug), which keeps it from a 5.

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 all four parameters are already documented, including 'brand id returned by search_brands'. The description's only real addition is framing brand_id, slug, and brand_name as alternative ways to identify the same brand; it does not state precedence or conflict behavior, so 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?

States a specific verb ('Get') and resource ('brand profile') and then enumerates exactly what the profile contains: description, website, company, aliases, rating, categories, product models. This is far more than the name restated and lets an agent distinguish it from search_brands, which only returns identifiers.

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?

Gives clear usage context by naming the three accepted identifiers and noting that brand_id comes from search_brands, which implies the search-then-fetch workflow. It stops short of explicit exclusions, e.g. which identifier wins if several are supplied, so it does not reach 5.

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