Skip to main content
Glama
vobiz-ai

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get account details

get_account_details
Read-only

Retrieve a Vobiz account profile by ID to view name, type, status, call limits, enabled features, and redacted credentials; requires main-account (MA_) access.

Instructions

Return this Vobiz account's profile (GET /Account/{id}): name, account type, status, CPS and concurrent-call limits and enabled features. Auth tokens and other secrets are replaced by "[redacted]". Only main-account (MA_) credentials can read it: with sub-account (SA_) credentials the forbidden error is returned, while get_account_balance, get_concurrency and list_phone_numbers still work. For money use get_account_balance; for live call capacity use get_concurrency.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
accountNoThe profile: auth_id, name, account type, status, CPS and concurrency limits, enabled features; secret fields hold "[redacted]".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "account": {
+      "additionalProperties": {},
+      "description": "The profile: auth_id, name, account type, status, CPS and concurrency limits, enabled features; secret fields hold \"[redacted]\".",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "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.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial context beyond them: credential-scope authorization rules, the specific failure mode for SA_ credentials, and the fact that auth tokens and secrets are returned as '[redacted]'. This is exactly the behavioral detail an agent needs before invoking.

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?

Three tight sentences, all load-bearing: the first defines the resource and payload, the second covers redaction, the third covers auth failure mode and alternatives. The routing information is front-loaded with no filler.

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-shape explanation is not required, and the description still summarizes the fields plus the redaction behavior. Combined with the explicit auth constraints and sibling routing, nothing an agent needs to call this correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter syntax or meaning for the description to add. The endpoint reference (GET /Account/{id}) hints at the implicit account identity, but no argument is exposed to document.

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 this Vobiz account's profile') and enumerates the exact fields returned (name, account type, status, CPS/concurrent-call limits, enabled features). It explicitly distinguishes itself from the closest siblings, get_account_balance and get_concurrency, so an agent can route correctly without opening schemas.

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 explicit when-not guidance: only main-account (MA_) credentials can read it, while sub-account (SA_) credentials return a forbidden error and should fall back to get_account_balance, get_concurrency or list_phone_numbers. It also names the two alternatives to use for money and live call capacity.

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