Skip to main content
Glama

Read a brand

playground_brand_get
Read-onlyIdempotent

Read the connected account’s selected brand and saved Brand DNA. Does not change the account’s active brand or apply the rules to a generation. Returns the selected brand’s saved Brand DNA and creative guidance.

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": {
      "brandId": "<brandId>"
    },
    "name": "playground_brand_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdYesSaved brand ID returned by brands_list; select the brand requested by the user.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
brandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: it explicitly says the active brand is not changed and no generation rules are applied, and that the payload is the saved Brand DNA plus creative guidance.

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?

Three short sentences, front-loaded with the action and scope. The final sentence partially restates the first ('saved Brand DNA' appears twice), a minor redundancy that keeps it from a 5.

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?

An output schema exists, so return values need not be spelled out, and the description covers scope, side-effect boundaries, and content of the result. Complete enough for a single-parameter read tool, though naming the sibling used to obtain brandId would close the last gap.

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?

Only one parameter and schema coverage is 100%, with the schema itself explaining that brandId comes from brands_list. The description adds no further meaning about the parameter, so the 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?

States a specific verb and resource: 'Read the connected account's selected brand and saved Brand DNA.' The singular 'selected brand' distinguishes it in spirit from a list tool, but the description never names playground_brands_list, so the agent must rely on the schema note to separate the two.

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 implied through exclusions ('Does not change the account's active brand or apply the rules to a generation'), which tells the agent what this is not for, but there is no explicit when-to-use statement or named alternative for finding brand IDs.

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.