Skip to main content
Glama

twilio_lookup

Check whether a phone number is valid and retrieve its country and national format using Twilio Lookup.

Instructions

(Beta) Look up a phone number with Twilio Lookup: whether it is valid, its country and national format, for...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It mentions the "(Beta)" status and the fields returned, which is useful, but says nothing about authentication requirements, rate limits, pricing/billing implications, or error behavior for invalid numbers. For a live third-party lookup call that is a meaningful gap.

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

Conciseness2/5

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

It is short, but it is truncated mid-sentence with a trailing "for...", so the reader cannot tell whether more behavior was meant to be described. Brevity here reflects incompleteness rather than disciplined editing.

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

Completeness2/5

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

With no annotations, no output schema, and no parameters, everything an agent needs must come from the description, and it is both truncated and silent on how the target number is chosen. The result shape is only partially sketched, and the caller cannot tell what happens on an invalid number.

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?

The schema declares zero properties, so per the baseline this would be a 4. However, the description asserts that a phone number is looked up while the tool accepts no input at all, and it never explains how that number is supplied (implicit, ambient, or config-bound). That unresolved discrepancy is a real semantic problem an agent must guess about.

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 names a specific verb and resource ("Look up a phone number with Twilio Lookup") and enumerates the key results: validity, country, and national format. That distinguishes it reasonably well from siblings such as twilio_list_numbers or twilio_search_available_numbers. It loses a point because the text is cut off mid-clause ("for..."), leaving the scope incomplete.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives. Nothing tells the agent why it would pick a Lookup-based validity/country check instead of list_numbers or search_available_numbers, and no prerequisites are given. The only contextual cue is the "(Beta)" marker.

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