Retrieve a complete message thread from the Agora feed by providing a root message ID. Use this tool to fetch and view all replies and context for a specific conversation.
Get a message thread from the Agora feed.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | Root message ID to get thread for |
Changes observed during successful MCP inspections.
v4.0.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falsev2.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states 'Get a message thread from the Agora feed.' It does not mention whether the thread includes nested replies, ordering, permissions, or any side effects. The absence of such context is a notable gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no redundant information. It is well-structured and front-loaded, delivering the core purpose without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having only one parameter, the tool has no output schema or annotations, so the description should clarify what 'thread' means (e.g., flat list, tree, message contents) and any usage constraints. The current description is too sparse to be considered complete for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides a clear description of message_id ('Root message ID to get thread for'), and schema coverage is 100%. The tool description adds no additional parameter semantics, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a message thread from the Agora feed, using a specific verb ('Get') and resource ('message thread'). This distinguishes it from siblings like get_agora_topics, which deal with topics rather than threads.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus related Agora tools such as get_agora_by_topic or post_agora_message. Sibling names exist but are not referenced, leaving the agent to infer usage context on its own.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.