Skip to main content
Glama

SMS inbox

spur_list_sms_conversations
Read-onlyIdempotent

SMS conversations with owners, newest first, with unread counts and the last message. Good for triaging replies (hot leads, not interested, wrong number).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum conversations to return
offsetNo
unread_onlyNotrue = only conversations with unread replies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety needs no restating. The description adds genuine context beyond them: result ordering (newest first) and the shape of each row (unread count and last message), which matters because there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the resource and ordering front-loaded and the triage use case trailing. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully discloses returned fields and sort order, which covers the most important unknown for a list tool. It falls short only on pagination behavior and the default/maximum page size, which an agent would otherwise learn only from the schema defaults.

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 coverage is 67% – limit and unread_only are documented in the schema, while offset is not described anywhere. The description's "newest first" hints at ordering but says nothing about pagination or when to set unread_only, so it does not compensate for the offset gap.

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?

The description states a specific resource (SMS conversations with owners) plus ordering (newest first) and payload contents (unread counts, last message), so an agent immediately knows this is an inbox listing. It does not explicitly contrast itself with siblings like spur_get_sms_conversation or spur_manage_sms_inbox, which keeps it out of 5 territory.

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?

"Good for triaging replies (hot leads, not interested, wrong number)" gives a usage scenario but no when-not conditions and no named alternative. An agent must infer on its own that reading a single thread belongs to spur_get_sms_conversation and inbox mutations to spur_manage_sms_inbox.

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