Skip to main content
Glama

Get the brand

get_brand
Read-only

Reads what Marsell knows about a project's brand: what it is, who it is for, how it talks, its line, colours, type and look, what it never does, its products (ids for make_pictures), and its own characters (each with its looks) and places. Write in this voice. The fuller context every picture and film is written inside: business_context_read.

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
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of what comes back (voice, colours, never-do rules, product ids, characters with looks) and by telling the agent to write in the returned voice. It says nothing about size, permissions or freshness, but the return-content disclosure goes well past the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening clause is well front-loaded with verb and resource, but the closing fragments 'Write in this voice.' and 'The fuller context every picture and film is written inside: business_context_read.' are telegraphic and easily misread as instructions or returned fields rather than routing hints. The enumeration is informative but the ending costs clarity.

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?

A read-only tool with one optional parameter and no output schema needs the description to convey return contents, and this one does so thoroughly. The only shortfall is the ambiguous relationship to business_context_read, which an agent may misread as an instruction to call a different tool instead.

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?

Schema description coverage is 100% and the single 'project' parameter already documents 'id or exact name' and its optionality when the account has one project. The description never mentions the parameter, so it adds no meaning beyond the schema; the baseline 3 applies.

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 (Reads) and resource (a project's brand), then enumerates what the brand record contains: identity, audience, voice, line, colours, type, look, prohibitions, products, characters and places. That level of detail lets an agent distinguish it from siblings like update_brand or add_brand_file without opening any schema.

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: 'its products (ids for make_pictures)' hints at a downstream consumer, and the trailing 'business_context_read' points at richer context, but it never states plainly whether to call this before make_pictures or in place of business_context_read. There are no explicit when-to-use or when-not-to-use conditions and no prerequisites.

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.