Skip to main content
Glama

Sparetext

List phones

list_devices
Read-onlyIdempotent

The user's phones: online or offline, how each sends (Android on its own; an iPhone through a Mac relay, a Shortcut while the app is open, or a tap on Send), whether it gets delivery reports, and which phone sends by default.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
devicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / devices / items / properties / mode / enum
      Previous value: -[
      -  "native",
      -  "relay",
      -  "shortcut",
      -  "assisted"
      -]New value: +[
      +  "native",
      +  "relay",
      +  "shortcut",
      +  "assisted",
      +  "api"
      +]
    • changedOutput schema / properties / devices / items / properties / platform / enum
      Previous value: -[
      -  "android",
      -  "ios",
      -  "mac"
      -]New value: +[
      +  "android",
      +  "ios",
      +  "mac",
      +  "provider"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / devices / items / properties / sims
      Added value: +{
      +  "description": "A dual-SIM Android phone's SIMs: each sends unless switched off, and Sparetext picks one for each text",
      +  "type": "array"
      +}
  3. Changed3 schema fields changed
    • addedOutput schema / properties / devices / items / properties / cappedUntil
      Added value: +{
      +  "description": "While a cap holds its texts: when it opens again",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / devices / items / properties / caps
      Added value: +{
      +  "description": "Texts it may send an hour and a day",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / devices / items / properties / giveUpAfter
      Added value: +{
      +  "description": "Seconds the phone may be offline before texts waiting for it are dropped",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  4. First observed

TDQS

A3.9/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, yet the description still adds substantial domain context: the distinct delivery paths per platform, whether delivery reports are enabled, and which phone is the default sender. It does not mention edge cases (e.g. no registered phones) or freshness of the online/offline signal, which keeps it below a 5.

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

Conciseness4/5

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

A single front-loaded sentence listing exactly the fields returned, with no filler or restatement of the title. The nested parenthetical of four send mechanisms is dense but each clause carries distinct information.

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

Completeness5/5

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

With zero parameters, full annotation coverage, and an output schema handling return structure, the description only needs to supply domain vocabulary, which it does for every returned attribute including the non-obvious relay and Shortcut paths. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly spends its space on output meaning instead of inventing parameter guidance.

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 names the resource (the user's phones) and enumerates the attributes surfaced: online/offline state, send mechanism (Android direct, iPhone via Mac relay, Shortcut while app open, or tap on Send), delivery-report support, and default phone. It is a noun-phrase inventory rather than an explicit verb+resource statement, but no sibling tool covers devices, so it is unambiguous which tool to pick.

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?

Use is only implied: the value of knowing device status and default sender is conveyed, but there is no explicit 'call this when...' trigger, no prerequisite, and no named alternative. Given a zero-parameter read tool with no competing sibling, the absence of explicit routing guidance is a small but real gap.

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