Skip to main content
Glama

get_business_brand

Read-onlyIdempotent

Read the approved business's saved brand colours, fonts, images and usage settings for website, campaign and Sales drafts.

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_business_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioral detail — that only the "approved" business's brand is returned — but says nothing about what happens when no brand has been saved or whether approval state gates the response.

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?

One front-loaded sentence that identifies the verb, the resource and the returned content types with no filler. It is tightly packed but slightly overloaded, bundling return contents and use contexts into a single clause.

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?

With no parameters, thorough annotations but no output schema, the description carries the return-value burden and does enumerate the fields returned. Complete enough to call correctly; only edge-case behavior (missing brand, approval gating) is unaddressed.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies a single implicit scope (the approved business) rather than a caller-supplied identifier.

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 description uses a specific verb ("Read") plus an enumerated resource ("brand colours, fonts, images and usage settings"), so an agent knows exactly what comes back. It implicitly contrasts with the write counterpart save_business_brand via "saved", but never names that sibling, so differentiation is inferred rather than stated.

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 through the phrase "for website, campaign and Sales drafts", which hints at where the brand assets are consumed. There is no explicit when-to-use statement, no exclusion, and no routing to save_business_brand for writing brand data.

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