Skip to main content
Glama

Resolve Brand Colour Standard Claim Detail

brand_guideline_claims
Read-onlyIdempotent

Resolves claim_id values (returned inline on every colour by brand_guideline_specify and brand_guideline_select) into their full claim record: source title/locator/citation, the exact permitted claim text, do_not_say restrictions, and claim_role (anchor/analogue/reject). Read-only: reads the already-persisted, frozen brand_ref snapshot; it does not re-run generation or mutate anything. Omit claim_ids to return every claim on the brand_ref. Accepts exactly one of brand_ref or project_id, same as brand_guideline_pdf.

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

Input Schema

NameRequiredDescriptionDefault
brand_refNoThe brand_ref returned by brand_guideline_specify or brand_guideline_select.
claim_idsNoWhich claim_id values to resolve. Omit (or pass an empty list) to return every claim on the brand_ref.
project_idNoAlternative to brand_ref for an authenticated (keyed) brand project. Requires the same API key that created it.
project_versionNoResolve claims against this specific immutable version instead of the project's current version.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, yet the description still adds substantive context: it reads an already-persisted, frozen brand_ref snapshot and does not re-run generation, and project_id requires the same API key that created the project. The only gap is that it does not mention behavior for unknown or stale claim_ids.

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 sentences, front-loaded with the core action and its return fields, then scoping rules. The first sentence is long and carries a parenthetical, but no sentence is filler and nothing is buried at the end.

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?

An output schema exists, so return values need not be described; annotations cover the safety profile; all four parameters are documented at 100% coverage; and the description still closes the loop on auth and snapshot semantics. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds a real constraint not expressed in the schema: exactly one of brand_ref or project_id must be supplied (mutual exclusivity is invisible in a schema with zero required parameters). The claim_ids omission/empty-list semantics are restated from the schema rather than extended, so this is a modest bump.

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 description opens with a specific verb+resource ("Resolves claim_id values ... into their full claim record") and enumerates exactly what comes back: source title/locator/citation, permitted claim text, do_not_say restrictions, and claim_role. It also names the sibling tools that produce claim_ids, so the agent can place it in the workflow without opening a schema.

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 gives clear operating context: claim_ids come inline from brand_guideline_specify/brand_guideline_select, omit them to get everything, and supply exactly one of brand_ref or project_id. It stops short of stating any explicit when-not-to-use condition or contrasting it against a competing sibling, which keeps it below a 5.

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