Skip to main content
Glama
Sign In
CP Brand MCP

CP Brand MCP

Official
by Consumer-Choice-Center
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_generation_prompt

Read-only

Prepares a CP one-pager brief using CP rules and clean layout slots, without generating factual claims or artwork.

Instructions

Prepare a CP one-pager brief using CP rules and clean layout slots. Does not generate factual claims or artwork.

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": {
      "request": "<request>"
    },
    "name": "create_generation_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.4.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and the non-persistent nature of "prepare" is consistent with them. The description adds a useful output boundary (no factual claims, no artwork), but says nothing about what the tool returns (a text prompt?), its length limits, or how CP rules are applied.

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 short sentences, front-loaded with the positive scope and followed by the exclusion; nothing is padded. The jargon ("CP rules", "clean layout slots") costs some clarity but not length.

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 one-parameter, read-only tool with no output schema, the definition should at minimum say what goes into the request and what comes back. It covers the negative scope well but leaves input expectations and return shape implicit, so an agent can guess the purpose yet not call it confidently.

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 parameter "request" has a 6000-char string schema with 0% coverage, so the description must carry the meaning and it does not: it never explains whether request holds a topic, a brand spec, layout slots, or free-form instructions. Only the max length constrains input, which comes from the schema, not the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Prepare a CP one-pager brief" gives a verb and a resource, but "CP" is an unexplained abbreviation and the name's term ("generation prompt") differs from the description's ("brief"), leaving ambiguity about what is actually produced. It also does not distinguish itself from close siblings such as create_one_pager, create_one_pager_visual_prompts, or create_central_visual_prompt.

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?

The only guidance is a negative scope statement ("Does not generate factual claims or artwork"), which hints at a boundary but never says when to pick this tool over create_one_pager or the other prompt builders. No prerequisites, no context about the pipeline stage where this belongs.

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

Deploy Server

Other Tools