Skip to main content
Glama

Outil.io

Get brand kit

get_brand_kit
Read-only

Lire la charte graphique du projet : logo (clair, sombre, icône), couleurs, polices, ton de voix, slogan, coordonnées et identité légale de l’entreprise (raison sociale, SIREN/SIRET, TVA, adresse…), avec version et champs manquants. À lire avant toute affiche, page légale, vidéo ou document commercial.

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

Input 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=true, openWorldHint=false, destructiveHint=false, so safety needs no restating. The description adds genuinely new behavioral context: the response carries a version and a list of missing fields, warning the agent that the kit may be incomplete. It does not discuss permissions or access requirements, keeping it short of a 5.

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 sentences, front-loaded with the resource and its contents, then the usage rule. The long comma-separated inventory of fields is dense but each item is substantive. Minor deduction for the list-heavy single sentence that is harder to scan than a short structured breakdown.

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?

With no output schema, the description carries the return-value burden and does so by naming the fields returned plus version and missing-field indicators. Combined with the usage trigger, an agent has everything needed to decide to call it and to 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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add. The enumerated content list functions as an informal return contract rather than a parameter explanation.

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 (read) and resource (the project's brand kit), then enumerates the actual contents: logos in three variants, colors, fonts, tone of voice, slogan, contact and legal identity. The read framing also implicitly separates it from the sibling update_brand_kit. An agent can identify it without opening the 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?

The final sentence gives explicit trigger contexts: read before producing any poster, legal page, video, or commercial document. It does not name update_brand_kit as the counterpart for modifications, but the read-vs-write distinction is clear from the verb alone.

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.