Skip to main content
Glama

List your brands

playground_brands_list
Read-onlyIdempotent

List brands owned by the connected account. Use when the user wants to choose existing brand rules. Does not select an active brand, open a project or spend credits. Returns the user’s saved brands and their identifying details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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 structurally. The description still adds real value by ruling out side effects an agent might otherwise assume — no active-brand switch, no project opening, no credit spend — and by confirming that saved brands plus identifying details come back.

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?

Three short sentences, front-loaded with the core action, then the usage condition, then the exclusions. Nothing is repeated from the title or annotations, and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, an output schema present, and rich annotations, the description only needs to establish purpose, trigger, and side-effect boundaries — all of which it does. An agent has everything required to decide whether to call it and what to expect.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the schema-level baseline applies. The description correctly implies an unscoped, account-wide listing rather than a filtered one, which matches the empty input object.

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 first sentence gives a specific verb and resource plus scope ('List brands owned by the connected account'), which is immediately distinguishable from a single-brand read like playground_brand_get. The description also makes clear what the call is not (brand selection, project opening), so an agent can place it precisely.

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?

It states a clear trigger ('Use when the user wants to choose existing brand rules') and three explicit non-triggers: it does not select an active brand, open a project, or spend credits. What is missing is a named alternative for the adjacent operations (e.g. the brand-get or brand-selection path), so routing is implied rather than fully directed.

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.