get_notificationFetch one visible ping by notification id, including its current action_state and, once anything on its data.checklist is checked, checklist_state.
| Name | Required | Description | Default |
|---|---|---|---|
| notification_id | Yes | Room notification id. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | A privacy-minimized, chainable PingRoom notification result. |
Changes observed during successful MCP inspections.
Output schema / properties / result / properties / checklist_stateAdded value: +{
+ "description": "Present once an item of data.checklist is checked: ticks[] of {index, checked_at, checked_by.display_name}. A checked item stays checked.",
+ "type": "object"
+}Output schema / properties / result / properties / origin_agentAdded value: +{
+ "description": "Present when a connected agent originated the ping: its handle and display name.",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: only *visible* notifications can be fetched (an access-scope constraint), and checklist_state is conditional on a checklist item being checked — a non-obvious behavioral trait.
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?
One sentence, front-loaded with the retrieval action and scoped by id, with the conditional return nuance tucked in a subordinate clause. No filler.
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?
For a single-param read tool with an output schema and full annotation coverage, this is nearly sufficient — purpose, access scope, and conditional field behavior are all present. The only soft spot is that it doesn't say what happens when the id refers to a non-visible or nonexistent notification.
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?
There is only one parameter and schema coverage is 100% (uuid, 'Room notification id'), so the schema already does the work — baseline 3 applies. The description restates 'by notification id' and adds the 'visible' qualifier, but no extra syntax or format meaning.
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?
States a specific verb and resource ('Fetch one visible ping by notification id'), which clearly distinguishes it from the sibling list_notifications by cardinality. It also names the salient return fields (action_state, checklist_state), so the agent knows what it gets back. It doesn't explicitly name sibling alternatives, but the singular-by-id scope is unambiguous.
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?
Usage is implied rather than stated: the agent can infer this is for retrieving a single known notification, versus list_notifications for enumeration or wait_for_notification for blocking. The word 'visible' hints at an access precondition, but there is no explicit when-to-use or when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.