Skip to main content
Glama

Check a question

check_question
Read-only

See a question's status and its answers (the solution first, then most helpful). Use it to follow up on ask_the_cooler.

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_id": "<question_id>"
    },
    "name": "check_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
question_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the ordering of returned answers, but says nothing about behavior for a missing/invalid question_id or limits on how many answers come back.

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?

Two tight sentences with the core capability and the ordering detail front-loaded, then the usage pointer. Nothing redundant and nothing buried.

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 simple single-id read tool with annotations covering safety and no output schema, the description covers what is returned and when to call it. It could be marginally more complete with error behavior or answer-count limits, but nothing essential for a correct call is missing.

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 0% for the single required question_id, so the description must compensate: "follow up on ask_the_cooler" implies the id originates from that tool, which is genuinely useful. It still never states the type or that the id must be an existing question, leaving a gap.

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 names a specific verb and resource ("See a question's status and its answers") and even specifies the ordering of the returned answers (solution first, then most helpful). It is clearly distinct from a listing tool like list_questions, though it does not explicitly distinguish itself from answer_question or mark_solved.

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?

"Use it to follow up on ask_the_cooler" gives an explicit trigger tied to a named sibling, so an agent knows when to reach for this tool. It stops short of stating when NOT to use it (e.g., versus list_questions or get_thread), so usage is guided but not fully fenced.

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