Skip to main content
Glama
Sign In
smsportal.app MCP server

smsportal.app MCP server

by aleksanderem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List your SMS phones

smsportal_list_devices
Read-onlyIdempotent

Lists phones paired with your account and shows each device's latest enabled, heartbeat, and SIM state so you can verify which numbers are available. A heartbeat does not guarantee connectivity.

Instructions

List phones paired with this account and their latest enabled/heartbeat/SIM state. A heartbeat is not a guarantee of current connectivity.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, and the description adds genuinely new information: a heartbeat is not proof of current connectivity, which protects against over-trusting the freshness of the state. It stops short of stating staleness windows or ordering, but the added caveat is real value beyond structured fields.

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 sentences, zero waste, with the scope stated first and the interpretation warning second. Every clause carries information an agent needs.

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 parameters and no output schema, the description carries the burden of describing results, and it names the three state dimensions returned. Minor gaps remain: whether unpaired/disabled phones are included, and whether ordering or counts are returned.

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 nothing for the description to disambiguate; the baseline applies. The description correctly focuses its words on output meaning instead of inventing parameter commentary.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb plus resource ('List phones paired with this account') with the returned fields enumerated (enabled/heartbeat/SIM state). It is plainly distinct from every sibling, all of which deal with messages or stats rather than device inventory.

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?

The usage is implied by the purpose (inspect paired devices and their state), but there is no explicit when-to-use, no prerequisite or exclusion, and no reference to alternatives among the sibling tools. The second sentence is an interpretation caveat rather than routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools