get_brand
Get full brand case-study details by slug (story, signature, logo tagline, industries)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Brand slug (e.g. 'porsche', 'google') |
Sense2 Promotional Products
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must convey behavioral traits. It implies a read-only retrieval operation but does not specify authorization requirements, error handling for invalid slugs, idempotency, or any side effects. It adds minimal behavioral context beyond listing returned fields.
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?
The description is a single, efficient sentence with no wasted words. It front-loads the purpose and lists key content, making it easy to parse quickly.
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?
Given the tool's simplicity (one parameter, no output schema), the description adequately covers the return value by listing main fields. It could be improved by mentioning idempotency or that it returns a single object, but it is sufficiently complete for a straightforward retrieval tool.
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?
The input schema covers 100% of parameters, and the single 'slug' parameter is described. The description adds value by enumerating the fields returned (story, signature, logo tagline, industries), which clarifies the output's meaning beyond the schema.
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 clearly states the tool retrieves full brand case-study details by slug, listing specific fields (story, signature, logo tagline, industries). The verb 'Get' and resource 'brand case-study details' are specific, and the use of a unique identifier (slug) distinguishes it from siblings like get_brands (which likely lists all brands).
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?
No guidance is provided on when to use this tool versus alternatives such as get_brands (list) or get_brand_moves (related brand moves). The description does not mention prerequisites, use cases, or when not to use it.
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.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool targets a distinct resource or action, from product and brand lookups to editorial collections and regional delivery info. Even similar listing tools (categories, industries, aesthetics, intents, inspirations, on-trend) are differentiated by their specific names and descriptions.
Naming Consistency4/5
The naming pattern is strongly consistent: lowercase with underscores, and almost all tools use the get_ prefix plus a resource name. The only deviation is search_products, which uses 'search' instead of 'get', but it still follows the verb_noun structure.
Tool Count3/5
With 21 tools, the server is on the heavy end of the typical range. The breadth is justified by the many distinct content types (products, brands, editorials, company info, reviews, regions, FAQ), but the count feels slightly bloated compared to leaner MCP servers.
Completeness4/5
The tool surface covers the full research and selection journey: product search, details, quotes, FAQ, company credibility, delivery areas, and inspirational content. The main gap is the lack of any transactional or order-placement tool, but that appears outside the intended scope.