Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Read an ad against the strategy

infer_strategy_cell_from_ad
Read-only

Given the text of an ad or hook (typically a competitor's), work out which audience, stage and pain point it targets in this site's strategy, how confident that is, a messaging brief drawn from it, and any audiences, pains or competitors it implies that the strategy does not have yet. Saves nothing — offer add_marketing_audience if the user wants a new audience. Needs a seeded strategy. Counts toward the hourly AI limit.

Input Schema

NameRequiredDescriptionDefault
ad_textYesThe ad copy or hook, verbatim
site_idYesThe site, from list_sites
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds genuinely useful context beyond them: 'Saves nothing', requires a seeded strategy, and 'Counts toward the hourly AI limit'. This discloses side effects and cost that the annotations alone do not.

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?

Front-loads 'Given the text of an ad or hook', then the output facets, then the constraints. Dense and mostly free of waste, though the first sentence runs long and packs several ideas together.

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?

With no output schema, the description does the work of describing the return facets (audience/stage/pain, confidence, brief, implied entities), plus prerequisite and cost. An agent has enough to call it correctly; only explicit failure behavior is unstated.

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 schema already documents all three parameters. The description reinforces that ad_text is verbatim ad copy and that site_id ties to a seeded strategy, but adds no syntax or format detail beyond the schema. 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 and resource: works out which audience, stage and pain point an ad text targets in the site's strategy, plus confidence and a messaging brief. An agent can distinguish this analytical read tool from add_marketing_audience 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?

Names the alternative explicitly ('offer add_marketing_audience if the user wants a new audience') and states the prerequisite ('Needs a seeded strategy'). Clear context for when to use, though there is no explicit when-not beyond the audience-saving routing.

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