Skip to main content
Glama

Dedicated number countries

search_dedicated_countries
Read-onlyIdempotent

Find countries that offer dedicated phone numbers, showing monthly price and stock status. Use the listed price as max_price_cents to buy one.

Instructions

List countries where dedicated numbers are offered, with your monthly price and stock status. A dedicated number is a private number that receives SMS from ALL services, renews monthly, and stays yours until you stop renewing. Next: show the user the price, then purchase_dedicated_number with it as max_price_cents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "countries": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "base_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "country": {
      +            "type": "string"
      +          },
      +          "in_stock": {
      +            "type": "boolean"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "quoted_price_cents": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "country",
      +          "name",
      +          "quoted_price_cents",
      +          "base_price_cents",
      +          "in_stock"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "countries"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.1.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is covered. The description adds real domain context beyond structured fields: what a dedicated number is (private, receives SMS from ALL services, renews monthly, persists until you stop renewing), which materially affects the buying decision.

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?

Three short sentences, front-loaded with the purpose, then the concept, then the next action. Every sentence earns its place and none is redundant.

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?

Output schema exists so return values need no explanation, and the description still names price and stock status. Combined with the explicit handoff to purchase_dedicated_number, an agent has everything needed to call it correctly.

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?

Zero parameters, so there is nothing to disambiguate and the baseline is 4. The description sensibly uses its words on product semantics instead of parameter explanation.

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?

Specific verb+resource: 'List countries where dedicated numbers are offered', and additionally states the returned fields (monthly price, stock status). This clearly distinguishes it from sibling product-search tools like search_sms_services and search_esim_plans.

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 an explicit downstream workflow: show the user the price, then call purchase_dedicated_number passing it as max_price_cents. This is actionable context, though it does not state exclusion conditions or name what to do if nothing is in stock.

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