Skip to main content
Glama
vobiz-ai

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get phone number details

get_phone_number_details
Read-only

Look up one account phone number by E.164 value to get status, capabilities, linked application, sub-account, fees, and billing dates.

Instructions

Return ONE phone number on this account by its E.164 value: status, capabilities, linked application, sub-account, fees and billing dates. The number must belong to this account or one of its sub-accounts; any other number returns the not_found error. To browse or search numbers use list_phone_numbers; for spam flags and call statistics use get_number_health.

Input Schema

NameRequiredDescriptionDefault
phone_numberYesThe number to look up, E.164 with or without the leading +, e.g. +919876543210. Must match exactly.

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
numberNoOne phone number as Vobiz returns it: e164, status, capabilities (voice, sms...), linked application, sub-account, monthly and setup fees, billing dates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / properties / phone_number / description
      Previous value: -"The number in E.164, e.g. +919876543210."New value: +"The number to look up, E.164 with or without the leading +, e.g. +919876543210. Must match exactly."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "number": {
+      "description": "One phone number as Vobiz returns it: e164, status, capabilities (voice, sms...), linked application, sub-account, monthly and setup fees, billing dates."
+    },
+    "ok": {
+      "description": "True on success; false when the result is an error (then error, message and retryable are set).",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context: the number must belong to this account or a sub-account, and any other number returns not_found. It does not mention auth scope or rate limits, so it falls short of a 5.

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?

Two sentences, no filler. The what-it-returns statement is front-loaded, followed immediately by the constraint and the sibling routing. Every clause carries information.

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 tool with an output schema (so return shape needn't be explained), all the decision-relevant facts are present: scope constraint, error behavior, and alternatives. The only redundancy is enumerating return fields that the output schema already provides.

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 description coverage is 100%, so the regex, E.164 format, examples, and 'must match exactly' semantics are already documented in the schema. The description's 'by its E.164 value' largely restates the parameter, adding only the ownership constraint on the value, which is the baseline-3 case for a fully-covered schema.

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 (return), resource (one phone number), lookup key (E.164 value), and enumerates the payload fields (status, capabilities, linked application, sub-account, fees, billing dates). The 'ONE' emphasis and named siblings make it clearly distinguishable from list_phone_numbers and get_number_health.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'To browse or search numbers use list_phone_numbers; for spam flags and call statistics use get_number_health.' Both alternatives are named with the condition that selects them, leaving nothing to inference.

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