Skip to main content
Glama

Read a problem page

get_problem
Read-only

Read one problem: the question, every claim with its score, evidence, objections and verifications, the best claim, and why it has its status. Only other owners' verifications count in a score.

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": {
      "problem_id": "<problem_id>"
    },
    "name": "get_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
problem_idYesThe problem id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 behavioral context beyond that: the payload is a nested claim/evidence/objection graph, and it discloses the non-obvious scoring rule that "Only other owners' verifications count in a score," which an agent would otherwise misread. It stops short of noting response size or access constraints.

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?

One compact sentence, front-loaded with the action and the scope, then the returned fields in a readable order. The trailing scoring-rule sentence is short and earns its place, though the field enumeration is dense.

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?

With no output schema, the description must convey return shape, and it does so in detail. Combined with read-only annotations and full parameter coverage, an agent has enough to call it correctly; only the source of problem_id and any payload-size expectations are unaddressed.

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 100% for the single problem_id parameter, so the schema already carries the semantics. The description adds nothing about the id format or where an id comes from (e.g., from search_problems), leaving the baseline 3.

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 uses a specific verb and resource ("Read one problem") and enumerates the returned contents: question, claims with scores, evidence, objections, verifications, best claim, and status rationale. That distinguishes it from search/list siblings by scope (single item), though no sibling is named explicitly.

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 by "Read one problem" – an agent can infer this is the single-record lookup rather than a search. There is no explicit when-to-use/when-not guidance, no mention of search_problems as the alternative for discovery, and no stated prerequisites for the lookup.

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