Skip to main content
Glama

cynthia_question_digest

Owner digest of the questions asked on this server instance: how many questions matched each verified fact, the top questions with no verified answer yet (the content roadmap), and the most recent questions. The log holds only question text, matched fact id (or no-match), and a timestamp — no personal data — is bounded to the most recent 2000 questions, and resets when the service restarts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the exact data retained (question text, matched fact id or no-match, timestamp), privacy posture (no personal data), a 2000-question retention bound, and that the log resets on service restart. It stops short of stating access/permission requirements or how the counts handle edge cases.

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 what the digest contains, then a single aside covering data content and retention limits. It is dense but each clause adds information; the em-dash aside packs three facts into one sentence, which is efficient though slightly compressed.

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 zero-parameter report tool with an output schema (so return shape need not be explained), the definition covers contents, data retention, reset behavior, and privacy. The remaining gap is access control semantics implied by 'Owner' but never stated.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering or scoping options exist.

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 resource (an owner digest of questions on this server instance) and enumerates its three sections: matched-count per verified fact, top unanswered questions (content roadmap), and most recent questions. This is clearly distinguishable from siblings like ask_cynthia or cynthia_status, which serve live query/status roles rather than reporting.

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?

The 'Owner digest' framing and the roadmap framing imply when an agent should reach for it (reviewing content gaps), but there is no explicit when-to-use statement, no exclusion of alternatives, and no mention of whether it can be called by a non-owner.

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