Skip to main content
Glama

cynthia_capabilities

Describe what Cynthia can do and the rules she follows (verified answers only, owner approval on risky actions, free-only building, subscription guard, and more).

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": "cynthia_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden of disclosure. It usefully enumerates the substantive policies that will be surfaced (verified answers only, owner approval on risky actions, free-only building, subscription guard), which is real domain context beyond the name. However, it never states the tool's own behavioral traits — that it is a read-only, side-effect-free documentation lookup with no parameters — leaving the safety profile implicit in the verb 'Describe'.

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?

Two lines with the core purpose stated first and the rule examples in a parenthetical aside, so nothing is buried. The enumerated rules border on restating return content that the output schema presumably already conveys, but the list is short and stays within budget.

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 no-parameter tool with an output schema, the description only needs to say what category of information comes back, and it does so with concrete examples. The one meaningful gap is the absence of any routing signal versus the sibling capability/status tools, which would matter to an agent choosing among them.

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 schema defines zero parameters with full coverage, so there is nothing for the description to disambiguate. No parameter guidance is needed and none is given, which is correct for this tool shape.

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 gives a specific verb ('Describe') and a specific resource ('what Cynthia can do and the rules she follows'), which is unambiguous for a zero-argument introspection tool. It does not name or differentiate against the siblings ask_cynthia and cynthia_status, leaving the agent to infer that this is the self-description endpoint rather than a query endpoint.

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 only implied: the tool tells the agent what Cynthia can do and which rules she follows, which suggests calling it for orientation before asking questions. There is no explicit guidance such as 'call this first' or a contrast with cynthia_status, so the agent must infer when this beats the alternatives.

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