Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Sextant brand kit

brand_get
Read-onlyIdempotent

Sextant's name, tagline, logo files, colours, fonts and layout style. Sextant has no Reports feature; this kit gives reports written from Sextant data (PDF, document, slides or page) Sextant's look.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds useful context about scope, notably that Sextant has no Reports feature and this kit supplies the visual identity for outbound artifacts. It stops short of saying what is actually returned (file payloads, URLs, or textual tokens), which is the one behavioural detail an agent still lacks.

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?

Two short sentences, but the second one is grammatically broken and requires re-reading to parse. The 'no Reports feature' clarification is buried mid-sentence rather than front-loaded where it would do the most routing work. Size is appropriate; execution is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with complete annotations, the definition covers what the kit contains and roughly why an agent would want it. With no output schema, however, the description should have stated the return shape (assets versus links versus style tokens), and it leaves that ambiguous. Adequate, with one real gap.

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 the baseline is 4 and there is no schema surface the description needs to compensate for. Nothing about inputs is missing or misleading.

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 names a concrete resource and enumerates its contents: name, tagline, logo files, colours, fonts and layout style. The retrieval verb is only implicit in the tool name 'get', but the object is unambiguous. It does not explicitly differentiate itself from the analytics siblings, though the domain difference is self-evident.

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: the second sentence gestures at producing branded reports (PDF, document, slides, page) from Sextant data. There is no explicit when-to-use or when-not-to-use statement, and no named alternative tool. The sentence is also grammatically tangled, which weakens the guidance it is trying to give.

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