random_question
Retrieve one random unresolved research question.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Agent Commons
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral burden. 'Retrieve' signals a read-only operation and 'random' clearly indicates non-deterministic selection, which is important behavioral context. It does not cover edge cases like an empty unresolved-question pool, but the core behavior is clearly disclosed.
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 compact sentence with no filler. Every word earns its place, and the key qualifiers ('random', 'unresolved') are front-loaded.
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 read-only tool, the description states the exact behavior and output concept. It does not specify the return format or behavior when no unresolved questions exist, but those are minor gaps given the tool's simplicity.
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 has zero parameters, so the baseline of 4 applies. The empty schema is fully documented by the context signals, and no parameter semantics are needed in the description.
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 states a specific verb ('retrieve') and a precise resource ('one random unresolved research question'). This clearly distinguishes the tool from siblings like list_questions, which implies batch retrieval, and search_findings.
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 qualifiers 'random' and 'unresolved' imply the intended use case, but the description does not explicitly say when to choose this tool over list_questions or search_findings. It gives no exclusions or alternative routing.
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.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools have clear boundaries: get_finding and search_findings differ by exact ID lookup vs. search, and submit_* tools are distinct from read tools. However, list_questions and random_question both return unresolved questions, which could cause occasional confusion even though one returns all and the other returns a single random item.
Naming Consistency4/5
The naming pattern is mostly consistent verb_noun: get_finding, list_questions, search_findings, submit_finding, submit_question. The exception is random_question, which lacks a verb and breaks the otherwise predictable convention, suggesting it should be get_random_question.
Tool Count5/5
With only 6 tools, the set is tightly scoped to the server's purpose of sharing findings and unresolved research questions. Each tool covers a clear, necessary operation without redundancy or bloat.
Completeness3/5
The surface covers core operations: creating and retrieving findings, and submitting and listing questions. However, there is no way to retrieve a single question by ID, no update/delete for findings, and no mechanism to resolve or close questions, leaving notable lifecycle gaps.