Clarifo

get_visual_cards_guide

Read-onlyIdempotent

Return the full authoring guide for generate_visual_cards (markdown).

Call this ONCE before authoring a VisualStoryContent v2 object. It documents everything the validator accepts — all 20 rich templates with when-to-use guidance, every chart type (including radial_gauge), annotations, key-figure tiles, segment rows, quotes, image effects, the editorial house rules (one card = one claim, headline/lede length budgets, no repetition) — and a gold-standard example story to pattern-match against.

Static content, no database or LLM call. Costs nothing on Clarifo's LLM budget.

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_visual_cards_guide"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds genuinely new facts: the return format is markdown, the content is static with no database or LLM call, and it costs nothing against the LLM budget. This is exactly the kind of cost/side-effect context annotations cannot convey.

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-loaded with the core action, then the usage rule, then supporting detail. The long em-dash enumeration of guide contents is dense but earns its place by telling the agent what it will get; the trailing cost line is short and useful rather than filler.

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 zero-argument, read-only static resource with an output schema present, nothing material is missing: the return medium is stated, the invocation timing is stated, and the side-effect profile is stated. The description need not describe response structure because the output schema carries that.

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 the baseline is 4 and there is nothing further to disambiguate. The description correctly makes no parameter claims, and the empty schema is fully consistent with a no-argument guide fetch.

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?

The first sentence names a specific verb (return) and resource (the full authoring guide for generate_visual_cards, in markdown), which is unambiguous and immediately distinguishes it from the sibling generate_visual_cards that produces the actual cards. The follow-up sentence enumerates what the guide contains, reinforcing its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger: 'Call this ONCE before authoring a VisualStoryContent v2 object', plus an explicit frequency constraint ('ONCE') and an explicit target tool it precedes (generate_visual_cards). The agent knows exactly when to invoke it and when not to repeat it.

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

All Clarifo tools Inspect

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.