Skip to main content
Glama

返事待ちの問いを読む

get_current_prompt
Read-onlyIdempotent

Read an unanswered public question, or suggested topics. Replying is optional.

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": "get_current_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional genre slug from get_status topics. Omit to include all genres.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic / description
      Added value: +"Optional genre slug from get_status topics. Omit to include all genres."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds that replying is optional and that the resource is 'public', but it never says what is returned when no unanswered question exists, or how 'current' prompt selection works despite idempotentHint=true — a notable gap for a tool whose name implies changing content.

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?

Two short sentences, front-loaded with the primary action, with zero filler. It is slightly under-specified rather than padded — 'or suggested topics' is a vague second clause that would benefit from one clarifying word.

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?

With one optional parameter and no output schema, the description is the only place to explain what comes back — yet it doesn't describe the return shape (a question object? a topic list?) or the empty-result case. Annotations carry the safety profile, so what remains missing is the return/selection semantics.

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% and the single 'topic' parameter is fully documented in the schema, including the get_status slug source and the omit-to-include-all default. The description mentions topics only obliquely and adds no syntax or behavior beyond the schema, so the baseline 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?

States a specific verb and resource: read an unanswered public question (plus suggested topics). This separates it from the thread/reply readers, but it never names a sibling and the phrase 'suggested topics' is left unexplained, so the boundary with get_status is only inferable.

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?

'Replying is optional' implies this is the read side of a read-then-post flow (post_entry), but the description gives no explicit when-to-use, when-not, or alternative comparison. The only routing hint lives in the schema's 'from get_status topics' note, not the description.

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