Skip to main content
Glama

Get brand kit

flypost_get_brand_kit
Read-only

Read the project brand kit: company, product, audience, tone, colors, fonts, logo, and its product screenshots (which flypost_design_visual can show). Call this before authoring content so drafts match the 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": "flypost_get_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project set with flypost_use_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds behavioral value beyond that: it discloses that the kit includes product screenshots whose display is handled by another tool, which is non-obvious cross-tool context. It does not say what happens when no brand kit has been configured, which keeps it below 5.

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?

Two sentences, no filler. The resource and its contents come first, the usage timing second, and the pointer to flypost_design_visual is folded into the parenthetical rather than given its own sentence.

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?

For a parameterless-in-practice read tool with no output schema, enumerating the returned fields effectively substitutes for a return description, and the call-before-authoring guidance covers sequencing. Nothing an agent needs in order to invoke it correctly is missing.

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

Parameters3/5

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

With one parameter at 100% schema description coverage, the schema already explains project_id and that omitting it uses the active project. The description adds no format, default, or fallback detail beyond that, so the baseline 3 applies.

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 (project brand kit) and then enumerates the exact contents returned: company, product, audience, tone, colors, fonts, logo, screenshots. This is clearly distinguishable from the mutating sibling flypost_update_brand_kit without opening either 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?

Gives an explicit call condition: 'Call this before authoring content so drafts match the brand,' which tells the agent exactly when this tool belongs in a workflow. It also points to flypost_design_visual as the consumer of the screenshots. It stops short of naming when-not-to-call or an alternative for reading brand data, so not a full 5.

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.