Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Write a cell's messaging brief

materialize_strategy_cell
Idempotent

Have our AI write the messaging brief for one strategy cell — the insight, hook, promise, proof points, call to action, tone and imagery direction for that audience at that stage with that pain — and save it on the strategy. A cell that already has a brief is returned as it is. Campaigns and landing pages need the brief first. Counts toward the hourly AI limit.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site, from list_sites
cell_keyYesA strategy cell: "persona_id:stage_id:pain_id" or "persona_id:stage_id:pain_id:competitor_id", ids from get_marketing_strategy
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations meaningfully: it discloses a metered cost ("Counts toward the hourly AI limit") and describes the exact idempotent semantics (existing brief returned unchanged), which is richer than idempotentHint=true alone. It does not say what happens for an invalid or unknown cell_key, nor anything about latency, so a 4 rather than 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?

Three tight sentences: what it writes, what it does when a brief exists, the ordering prerequisite, and the cost. Nothing repeats the annotations or title, and the core action leads.

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?

For a generative write tool with no output schema, the description covers the artifact's contents, where it is stored, no-op behavior, and billing impact. Only the returned payload shape and error behavior for a bad cell_key are left implicit.

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?

Schema description coverage is 100%, so the baseline is 3. The description's "that audience at that stage with that pain" loosely mirrors the persona:stage:pain key format already documented in the schema, and user_goal is never mentioned. It adds no syntax or constraint information the schema lacks.

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 and resource ("write the messaging brief for one strategy cell") and enumerates exactly what the brief contains (insight, hook, promise, proof points, CTA, tone, imagery). A final clause ("save it on the strategy") makes clear it materializes and persists rather than returning a draft, which separates it from idea/draft siblings.

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?

"Campaigns and landing pages need the brief first" gives a concrete prerequisite that positions it ahead of spawn_campaign_landing_page and draft_campaign, and "A cell that already has a brief is returned as it is" tells the agent when the call is a no-op. It stops short of naming an alternative tool or a hard exclusion, 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.

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources