Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

check_mobile_advanced

check_mobile_advanced
Read-onlyIdempotent

Retrieve advanced information for a mobile number using its international prefix to verify validity, identify carrier and line type, and assess fraud and abuse risk.

Instructions

Retrieves advanced information about a mobile number (requestedNumber, formattedNumber, createdAt, updatedAt, state, message, success, valid, active, localFormat, fraudScore, recentAbuse, voip, prepaid, risky, name, identityData, carrier, lineType, country, region, city, accurateCountryCode, zipCode, timezone, dialingCode, doNotCall, leaked, spammer, activeStatus, mcc, mnc, transactionDetails) 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_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
mobileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety behavior is covered. The description adds useful transparency by naming the expected result fields, including fraudScore, recentAbuse, leaked, spammer, carrier, identityData, and transactionDetails, which helps an agent understand the richness of the lookup.

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

Conciseness3/5

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

The purpose is front-loaded, but the description is dominated by an unstructured parenthetical list of roughly 30 result fields and an awkward inline 'Args:' line. The field list is useful because no output schema exists, but its presentation is dense and could be organized more clearly.

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

Completeness3/5

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

For a one-parameter read-only lookup with no output schema, the description covers the input format and expected return fields. However, it lacks guidance on when to choose this tool over check_mobile_start and gives no information about error behavior, rate limits, or authentication needs.

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?

With 0% schema description coverage, the description must compensate for the single parameter. It does so by specifying 'mobile: with international prefix es +39,' giving an agent the critical format expectation, though it does not clarify whether spaces, plus signs, or local formats are accepted.

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 states a specific verb and resource: 'Retrieves advanced information about a mobile number,' and enumerates the returned data categories. It does not explicitly contrast itself with sibling check_mobile_start, so an agent must infer the 'advanced' distinction from the name and description.

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 by the word 'advanced' and the long list of detailed fields. There is no explicit guidance such as when to use this instead of check_mobile_start, or any stated prerequisites for a more detailed lookup.

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