Skip to main content
Glama

detect_brand_identity

Read-onlyIdempotent

Extracts existing source colors, font declarations, and real headings from a project to document its brand identity without inventing new branding.

Instructions

Extract existing source colors, font declarations and real headings without inventing branding.

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": {
      "project": "<project>"
    },
    "name": "detect_brand_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral claim beyond that: it reports only declarations found in the source and does not fabricate branding, which sets a fidelity expectation. It says nothing about what happens when no colors or fonts are found, so a mid score is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the extraction target front-loaded and a scope constraint appended. Every clause carries meaning and nothing is padded.

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?

An output schema exists, so return values need not be explained, and the read-only annotations cover safety for a simple one-parameter tool. The remaining gap is the undocumented "project" input and the absence of any note on empty or unbranded sources, which leaves the definition only minimally viable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter "project" has 0% schema description coverage and is never mentioned in the description. The agent gets no hint about what a project identifier is, its format, or where it comes from, so the description fails to compensate for the coverage gap.

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 ("Extract") and enumerates the exact resources produced: source colors, font declarations, and real headings. That is far more informative than the name alone and lets an agent distinguish it from broad siblings like analyze_project or inspect_media_assets, though no sibling is named as a contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no prerequisites, and no routing to alternatives such as analyze_project. The only usage-adjacent signal is the implicit constraint "without inventing branding," which tells the agent this reads from existing source rather than generating, but it is not framed as guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.