Skip to main content
Glama

List brand kits

list_brands
Read-only

The brand kits saved in the studio. Start here: pass a kit's id as brand_id to the other tools instead of a full brand.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

readOnlyHint=true already tells the agent this is a safe read. The description usefully adds that the returned kit ids are reusable as brand_id elsewhere, but says nothing about what a kit record contains (id, name, etc.) or ordering, and there is no output schema to cover that.

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?

Two short sentences with zero filler, and the primary instruction ("Start here") is front-loaded immediately after the one-line resource statement.

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?

For a simple, parameterless discovery tool with annotations covering safety, the definition supplies what an agent needs to call it and what to do with the result. The only missing piece is a hint at the shape of each returned kit.

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 no parameters, so the schema baseline is 4. The mention of brand_id refers to other tools' inputs rather than this one, which is contextual guidance rather than parameter documentation.

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?

"The brand kits saved in the studio" names the exact resource returned, and combined with the tool name the listing action is unambiguous. It is distinguishable from get_brand (single kit) and save_brand (write), though the description itself never uses an explicit verb.

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?

"Start here" is explicit sequencing guidance, and "pass a kit's id as brand_id to the other tools instead of a full brand" tells the agent both the follow-up action and the preferred shorthand. It lacks an explicit when-not condition, but for a zero-parameter discovery tool that is a small gap.

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