Skip to main content
Glama

Read a brand

read_brand
Idempotent

Reads a company's brand from its own public site: its name, its brand colour, the colours and type it is set in, and whether it has a logo. The brand is kept on the account to set artifacts in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "read_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe company's domain, like acme.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and, notably, readOnlyHint=false; the description explains that gap by stating the brand is kept on the account, i.e. the call persists state despite being a "read". It also discloses the external dependency on the company's own public site, which implies network failure modes. It does not describe behaviour when no brand can be found on the site.

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 tight sentences with the returned fields front-loaded and no filler. The clause "the colours and type it is set in" is slightly awkward phrasing but carries information rather than padding.

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?

There is no output schema, so the description appropriately enumerates the returned attributes and notes the side effect of storing the brand on the account. For a single-parameter read tool this covers what an agent needs to call it and interpret the result.

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?

With one parameter at 100% schema coverage the schema already defines the domain, but the description adds a real constraint: the domain must resolve to the company's own public site for a brand to be read. That is meaning beyond the schema's format example.

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 gives a specific verb and resource ("Reads a company's brand") and enumerates what is returned: name, brand colour, colours and type, and logo presence. It is clearly distinct from generic siblings like get_company or get_artifact, though it never names a sibling to contrast against.

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?

"The brand is kept on the account to set artifacts in" implies the downstream use (styling artifacts) but never states when to call this versus get_company or style_artifact. Usage must be inferred from the mention of artifacts rather than from an explicit when-to-use rule.

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