Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

check_mobile_start

check_mobile_start
Read-onlyIdempotent

Retrieves basic details about a mobile number, including validity, type, region, network, and porting status, using an international-prefixed number.

Instructions

Retrieves basic information about a mobile number (requestedNumber, formattedNumber, numberType, isPossible, isValid, regionCode, isValidNumberForRegion, network, originalNetwork, roaming, ported, country, countryPrefix, details) Args: mobile: with international prefix es +39

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mobile": "<mobile>"
    },
    "name": "check_mobile_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
mobileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description earns credit for enumerating the fields returned (numberType, isPossible, isValid, regionCode, network, ported, roaming, etc.), which is real behavioral information given there is no output schema. It does not say what happens on invalid input or whether invalid numbers return an error versus an isValid=false payload, which is the main residual gap.

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?

The first sentence is front-loaded and earns its place, and the field list is dense but useful because no output schema exists. Minor deduction for the awkward 'Args:' block and the malformed prefix example, which add roughness without adding clarity.

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?

For a single-parameter read-only lookup with no output schema, the definition covers purpose, input format and the shape of the result. What is missing is the failure/edge semantics (unparseable number, non-geographic or non-Italian prefixes) and an explicit pointer to check_mobile_advanced for deeper detail.

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?

Schema coverage is 0%, so the description carries the burden, and it does supply the essential constraint: the number must be supplied with international prefix. The example is garbled ('es +39' rather than something like 'e.g. +393401234567'), so the intent is clear but the illustration is imprecise and does not cover non-Italian prefixes despite the tool returning a regionCode and countryPrefix.

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?

Specific verb ('Retrieves') plus resource ('basic information about a mobile number'), and the word 'basic' implicitly positions it against the sibling check_mobile_advanced. It does not name that sibling outright, so the differentiation is inferable rather than stated.

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?

Usage is only implied: 'basic information' suggests the lighter-weight check versus check_mobile_advanced, but no explicit when-to-use or when-not-to-use condition is given. The one practical hint supplied is a formatting rule for the input, which is parameter guidance rather than selection guidance.

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