Skip to main content
Glama

get_brand

Read-only

Retrieve the community's brand identity—name, tagline, site, colours, and logo—so generated videos and captions use the correct branding and tone.

Instructions

Identity of this instance: the community's name, tagline, site, colours and logo. Videos carry this brand automatically (animated intro/outro built from the logo, HUD, captions); use the name and tone when writing titles or captions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: the brand is applied automatically to videos (animated intro/outro from the logo, HUD, captions), telling the agent it does not need to pass brand data through to rendering steps. It stops short of describing the return shape, but the output schema covers that.

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?

Two sentences, front-loaded with the identity payload and followed by the practical consequence. Every clause carries information; the only minor friction is the slightly elliptical opening phrase "Identity of this instance" instead of a direct verb.

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 zero-parameter, read-only getter with an output schema, the description covers what is returned and how the brand propagates into video output. An agent has enough to call it correctly and interpret the result, though a hint on when brand data is irrelevant would round it out.

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 baseline of 4 applies. The description's mention of specific brand fields is informative but does not function as 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?

It names the specific resource returned — the community's name, tagline, site, colours and logo — so an agent knows exactly what this fetches, unlike sibling tools such as get_capabilities or get_feed. It lacks an explicit verb ("returns" / "retrieves"), but the resource list is concrete enough to remove ambiguity.

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?

It gives downstream usage guidance ("use the name and tone when writing titles or captions"), which implies this should be consulted before authoring content. However, it names no alternative tool and states no when-not condition, so routing guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.