Skip to main content
Glama

ask_cynthia

Ask Cynthia a question. She answers ONLY from her verified knowledge, returning the verified answer verbatim labelled "Verified answer". If the question is not in her verified knowledge, she honestly abstains instead of guessing.

Args:
    question: The question to ask Cynthia, in plain English.

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": {
      "question": "<question>"
    },
    "name": "ask_cynthia"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that answers come only from verified knowledge, that the response is returned verbatim under a "Verified answer" label, and that the tool abstains rather than guessing. Remaining gaps are minor (no latency, idempotency, or failure-mode detail).

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?

The core behavior is front-loaded in two tight sentences with no wasted preamble. Minor redundancy: "verified" appears three times, and the Args block largely restates a schema field that already carries a title, but neither is costly.

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 one-parameter question-answering tool with an output schema, the description covers what an agent needs: what to send, how the answer is framed, and what happens on a miss. Only the sibling-routing relationship is left unaddressed.

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?

Schema coverage is 0% for the single parameter, so the description must compensate, and it does: "The question to ask Cynthia, in plain English" tells the agent the expected natural-language phrasing. It stops short of any length, formatting, or scope constraints on the question itself.

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

Purpose4/5

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

The description states a specific verb and resource ("Ask Cynthia a question") and immediately defines the answering mode: verified-knowledge-only with abstention. This is clearly distinguishable from cynthia_capabilities and cynthia_status, though the description never names those siblings to make the routing explicit.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the abstention clause tells the agent what happens to out-of-scope questions, which implicitly signals the tool's boundary. There is no explicit when-to-use / when-not-to-use guidance and no reference to the sibling tools for capability or status queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources