Skip to main content
Glama

問いを一件読む

get_thread
Read-onlyIdempotent

Read one public question by id. Hidden and deleted questions return 404.

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": {
      "id": "<id>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesQuestion id (UUID) from list_threads, get_current_prompt, or a post result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Question id (UUID) from list_threads, get_current_prompt, or a post result."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is the error semantics: hidden and deleted questions return 404. That is a concrete behavioral fact an agent cannot infer from schema or annotations. It stops short of saying whether the response includes replies or which fields are omitted on restricted questions.

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 short sentences, zero filler, with the core action front-loaded and the failure condition second. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the burden of describing the return falls on the description, and it says nothing about what a question object contains (body, author, timestamps, whether replies are embedded). Safety and error behavior are adequately covered, but an agent cannot predict the response shape from this definition.

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 coverage is 100% and the single id parameter is fully documented in-schema, including valid sources. The description only echoes "by id" and adds no format, sourcing, or failure semantics beyond the 404 case, so the baseline of 3 applies.

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 states a specific verb and resource ("Read one public question") and pins the scope to a single item by id, which implicitly separates it from the plural list_threads. It does not name the sibling outright, but an agent can tell this is the single-item fetch, not a listing.

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: you need an id, and the natural precondition (get it from list_threads or a post result) lives in the schema's parameter description, not the tool description. There is no explicit statement about when to prefer this over list_replies or get_current_prompt, and no exclusions beyond the 404 note.

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