Cleotic

Get narrative

get_narrative

Read-onlyIdempotent

One reputation narrative from get_reputation: the questions it appears in, the latest quotes per engine with answer IDs for get_answer, its alerts, and any decision a person made on it.

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": {
      "brand": "<brand>",
      "narrative_id": "<narrative_id>"
    },
    "name": "get_narrative"
  }
}

Input Schema

Name	Required	Description	Default
`brand`	Yes	Brand or study: its ID from list_brands, or its name (exact or a unique prefix).
`narrative_id`	Yes	Narrative ID from get_reputation.

Output Schema

Name	Required	Description
`data`	Yes
`generated_at`	Yes	RFC 3339 time the response was made.
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description's main added value is payload composition. It usefully discloses that the result includes alerts and human decisions, though it does not discuss pagination or response size.

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?

The description is a single front-loaded sentence with a colon-delimited payload list. Every clause contributes either scope or a useful pointer to related tools.

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?

Given full schema coverage, a rich annotation set, and an output schema, the description provides enough context for correct selection and invocation. It also summarizes the returned contents and cross-references get_reputation and get_answer.

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%, and both required parameters are documented in the schema. The description reinforces that narrative_id comes from get_reputation, but adds little beyond the schema's own parameter descriptions.

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 description identifies a specific resource—one reputation narrative—and explicitly says it comes from get_reputation. It also enumerates the payload: questions, engine quotes with answer IDs, alerts, and human decisions, distinguishing it from sibling list/detail tools.

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?

It clearly situates the tool after get_reputation by stating the narrative comes from there, and it points to get_answer for quote-level detail. It does not explicitly state when not to use it or compare it directly with get_perception, but the retrieval context is clear.

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

All Cleotic 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.

Resources

Need Help?