Skip to main content
Glama

Brand architecture

brand_architecture_planner
Read-only

Suggest a brand architecture model per product. Give products as lines 'Name | audience=same | category=overlap | risk=low | standalone=no | acquired=no' (or objects with those keys) and optionally company. audience and category take same, overlap or different relative to the parent; risk is the chance a problem with one damages the other (low, medium, high); standalone says whether it needs an identity that can live alone; acquired says whether you bought it. Returns branded house, house of brands or endorsed brand for each with scores, the reasons, which facts were missing and treated as neutral, an example naming pattern, and an overall tally with a note when the portfolio is mixed. Scoring is our own simple rule, a starting point for discussion.

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": {
      "products": "<products>"
    },
    "name": "brand_architecture_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNoParent company or master brand name
productsYesProducts, one per line as 'Name | key=value | ...', or an array of objects

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this a read-only, closed-world, non-destructive operation, so the safety profile is covered. The description goes further by disclosing the return anatomy (per-product models with scores and reasons, missing facts treated as neutral, an example naming pattern, and a portfolio tally with a mixed-portfolio note) and by flagging that the scoring heuristic is deliberately simple. It does not state any limits on portfolio size.

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?

Front-loaded with the action, then input format, then returns, then a caveat – a logical order with no filler. Despite dense parentheticals every clause carries new information the agent needs to call the tool correctly.

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 return-value burden and does so thoroughly, including the neutral-facts behavior that an agent must know to interpret scores. Minor gap: no guidance on how many products are reasonable or what happens on malformed input lines.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real semantics: the exact pipe-delimited line format for `products`, the permitted values for audience/category (same, overlap, different) and risk (low, medium, high), and the meaning of standalone and acquired. This supplies enum-like guidance the schema lacks entirely and clarifies the string-vs-object alternative.

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 ('Suggest a brand architecture model per product') and bounds the output set to branded house / house of brands / endorsed brand. No sibling tool covers brand architecture, so this is unambiguously distinct from loose neighbours like brand_voice_consistency or naming_check.

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 only implied: the agent learns it should supply products (and optionally a company) for an architecture decision, but there is no explicit 'use this when…' framing, no exclusions, and no named alternative. The closing caveat that the scoring is a simple rule and 'a starting point for discussion' does helpfully set expectations about when to trust the result.

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