Retrieve recent messages from a Twake Chat room by providing its room ID, with an optional limit for the number of messages to fetch. Use it to access conversation history for context or analysis.
Get recent messages from a Twake Chat room
| Name | Required | Description | Default |
|---|---|---|---|
| room | Yes | Room ID | |
| limit | No | Max messages (default 20) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burdon of behaviordisclosure. 'Get' signals a read-only operation, but the description does not disclose ordering, pagination, or how 'recent' is determined beyond the optional limit parameter. This is a meaningful gap for a no-annotation tool.
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, front-loaded sentence with no filler. It communicates the core operation clearly and is appropriately sized for the simplicity of the tool.
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?
The description adequately conveys the basic purpose for a simple read tool, but the absence of an output schema and annotations leaves return shape and behavioral details unspecified. Sibling context helps distinguish the tool but does not fill the missing ordering and pagination information.
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?
Schema description coverage is 100%: room is documented as 'Room ID' and limit as 'Max messages (default 20)'. The description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.
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 uses a specific verb and resource: 'Get recent messages from a Twake Chat room'. It is clearly distinct from sibling tools like twake_chat_send and twake_chat_rooms, though 'recent' is not precisely defined.
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?
There is no guidance on when to use this tool versus alternatives such as twake_search or twake_chat_rooms. The description only states what it does, not when it should be preferred or avoided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.