Skip to main content
Glama
Sign In
vobiz-ai

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get phone number health

get_number_health
Read-only

Check spam flags, usage status, and call statistics (answer rate, failed calls, minutes) for a phone number to judge if a caller ID is flagged or over-used.

Instructions

Return usage and health of one phone number on this account (GET /numbers/{e164}/health): spam flag, usage status and call statistics (answer rate, failed calls, minutes) bucketed per day or per hour. Use it to judge whether a caller ID is being flagged or over-used; for the number's configuration and fees use get_phone_number_details. days sets the history window for daily granularity only and is ignored for hourly.

Input Schema

NameRequiredDescriptionDefault
daysNoDays of history for daily granularity, 1-90 (default 30). Ignored when granularity is hourly.
granularityNoBucket size for the statistics: daily (default) or hourly.
phone_numberYesThe number to inspect, E.164 (leading + optional); must be on this account.

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
healthNoVobiz's health report: spam flag, usage status and the per-day or per-hour statistics (calls, answered, failed, answer rate, minutes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.4.2
    • changedInput schema / properties / days / description
      Previous value: -"Days of history for daily granularity (default 30, max 90)."New value: +"Days of history for daily granularity, 1-90 (default 30). Ignored when granularity is hourly."
    • changedInput schema / properties / granularity / description
      Previous value: -"Default daily."New value: +"Bucket size for the statistics: daily (default) or hourly."
    • changedInput schema / properties / phone_number / description
      Previous value: -"The number in E.164."New value: +"The number to inspect, E.164 (leading + optional); must be on this account."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "health": {
+      "description": "Vobiz's health report: spam flag, usage status and the per-day or per-hour statistics (calls, answered, failed, answer rate, minutes)."
+    },
+    "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 beyond that: the endpoint is read-only, the data is bucketed per day or per hour, and the `days` window is silently ignored under hourly granularity — a non-obvious quirk. It stops short of mentioning auth requirements, rate limits, or history retention limits.

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?

Front-loads the purpose, then the use case, then the parameter caveat — a good information order with no filler sentences. It is slightly padded by repeating the `days`-ignored-for-hourly rule that the schema already states, which is the only wasted clause.

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?

An output schema exists, so return values need no explanation. The description covers what is returned, when to choose it over the sibling, and the one parameter interaction an agent could get wrong (days with hourly granularity), leaving no material gap for a 3-parameter read tool.

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 phone_number, granularity, and days are all already documented in the schema, including the enum values and the daily-only behavior of `days`. The description largely restates that same `days` constraint rather than adding new semantics, so the baseline 3 applies.

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+resource ('Return usage and health of one phone number on this account'), names the underlying endpoint, and enumerates the returned facets (spam flag, usage status, answer rate, failed calls, minutes). It explicitly distinguishes itself from get_phone_number_details, so an agent can separate the two without opening either schema.

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?

Gives an explicit use case ('judge whether a caller ID is being flagged or over-used') and routes the agent to a named alternative for the contrasting need ('for the number's configuration and fees use get_phone_number_details'). The granularity/window interaction is also called out, 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