Skip to main content
Glama

Search SMS services

search_sms_services
Read-onlyIdempotent

Search US non-VoIP SMS services for OTP and phone verification, comparing one-time verification and long-term rental prices; filter by service name to find a number and price.

Instructions

Search US non-VoIP SMS services (OTP / phone verification) with your prices: the one-time verification price and, when offered, long-term rental prices. Shows up to 50 rows; pass query to narrow by service name. Next: show the user the price, then rent_number with the svc_ id and that price as max_price_cents.

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

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive substring of the service name (e.g. 'telegram').

Output Schema

NameRequiredDescriptionDefault
totalYes
servicesYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.2.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "services": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "available": {
      +            "type": "boolean"
      +          },
      +          "base_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "icon_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "ltr_14d_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "ltr_30d_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "ltr_3d_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "ltr_7d_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "price_ceiling_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "quoted_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "quoted_price_cents"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "services",
      +    "total",
      +    "truncated"
      +  ],
      +  "type": "object"
      +}
  3. Changed2 schema fields changedv1.1.8
    • changedInput schema / properties / query / description
      Previous value: -"Substring filter on service name (e.g. 'telegram')."New value: +"Case-insensitive substring of the service name (e.g. 'telegram')."
    • addedInput schema / properties / query / maxLength
      Added value: +80
  4. First observedv1.1.3

TDQS

A4.1/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 closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: a hard 50-row cap, which price fields are returned (one-time verification vs long-term rental), and the downstream contract that the displayed price should become max_price_cents. It does not say how truncation at 50 rows is indicated or whether results reflect live stock.

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?

Two sentences, front-loaded with scope and capped with an actionable next step; nothing is filler. The phrase 'with your prices: the one-time verification price and, when offered, long-term rental prices' is slightly tangled but still readable.

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?

An output schema exists, so return-value detail is not required, and the description still summarizes the price shape. Combined with the 50-row cap and the rent_number handoff, an agent has enough to act; only result-truncation and stock-freshness behavior remain unstated.

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 100% for the single optional parameter, and its description already defines it as a case-insensitive substring with examples. The description only restates 'pass query to narrow by service name', adding no format or matching nuance beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource plus the exact scope: 'Search US non-VoIP SMS services (OTP / phone verification)'. The domain qualifier (non-VoIP, US, OTP) separates it cleanly from siblings like search_dedicated_countries, search_esim_plans and search_proxies without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete when-to-use rule ('pass query to narrow by service name') and an explicit next-step chain: show the price, then call rent_number with the svc_ id and that price as max_price_cents. It stops short of saying when to prefer a sibling (e.g. dedicated-country search) instead, so the exclusion side of the guidance is missing.

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