Skip to main content
Glama
Content Drifter MCP

Content Drifter MCP

Official
by OPTRIXTECH

get_brand_kit

Read your Brand Kit settings—voice, colors, fonts, and CTA—to keep generated social content suggestions on-brand.

Instructions

Read the user Brand Kit (voice, colors, fonts, CTA) to keep suggestions on-brand.

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. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the key traits: this is a read operation scoped to the current user's Brand Kit, and it returns four named content categories. It does not say what happens if the kit is empty or unconfigured, which is the main remaining behavioral gap for a zero-param read.

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 sentence, verb-first, with the resource and its contents front-loaded and the downstream purpose at the end. No filler words and nothing redundant.

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?

There is no output schema, so naming the four returned categories (voice, colors, fonts, CTA) usefully compensates, and no input parameters need explaining. The only omission is edge-case behavior when no Brand Kit exists, which is minor for a simple read.

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 there is nothing for the description to disambiguate; baseline for a no-param tool is 4. The parenthetical field list usefully describes the response shape rather than inputs, which is the only relevant semantic detail here.

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?

States a specific verb and resource ('Read the user Brand Kit') and enumerates its contents (voice, colors, fonts, CTA), so an agent knows exactly what data comes back. It does not explicitly differentiate itself from siblings like generate_post, though the 'keep suggestions on-brand' framing implies it is a prerequisite read.

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 clause 'to keep suggestions on-brand' implies when to call it (before generating content), but usage is only implied. There is no explicit when-not guidance, no statement about whether it should always be called first, and no mention of behavior when the user has no brand kit configured.

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