Manage unread SMS
spur_manage_sms_inboxRead the unread count, page inbound replies, or mark specific messages read after triage.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
spur_manage_sms_inboxRead the unread count, page inbound replies, or mark specific messages read after triage.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered; the description's contribution is disclosing which of the three branches mutates state (mark_read). It says nothing about whether marking read is reversible, whether already-read IDs are tolerated, or how paging behaves at the 100-item cap, leaving real behavioral gaps for the mutating path.
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?
A single sentence that front-loads all three actions in the same order as the schema branches, with zero filler and no redundancy. Nothing could be removed without losing an operation.
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 three-branch discriminated tool, the description covers every branch and flags the one that writes state, which is the key completeness requirement here. Remaining shortfalls — pagination semantics and return shape — are either constrained in the schema (default 20, max 100) or excused by the absence of an output schema.
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 coverage is reported at 100%, so the parameters are structurally documented and the baseline is 3. The description only loosely hints at the parameter usage — 'page' gestures at limit/unread_only and 'specific messages' gestures at message_ids — without adding format, ordering, or semantics beyond what the oneOf branches already convey.
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 names three concrete operations that map exactly onto the three schema branches: reading the unread count, paging inbound replies, and marking specific messages read. It is a specific verb+resource statement rather than a restatement of the title, but it never distinguishes itself from adjacent SMS tools such as spur_get_sms_conversation or spur_list_sms_conversations, so the agent must infer the boundary.
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?
The phrase 'mark specific messages read after triage' implies a workflow ordering for the mutating branch, which is genuinely useful. However, there is no when-not guidance, no mention of which sibling to use for reading full conversation threads versus paging replies, and no prerequisites stated.
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.