Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get call concurrency

get_concurrency
Read-only

Check live call capacity before bulk dialing: returns concurrent calls running now, the maximum allowed, and utilization percentage, so you can avoid hitting the concurrency limit.

Instructions

Return this account's live call capacity (GET /concurrency): concurrent_calls running right now, the max_concurrent the account may run and utilization_pct. It is a count, not a list: to see which calls are live use list_live_calls. Use it before a batch of make_call requests to avoid hitting the concurrency limit.

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).
concurrencyNo

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": {
+    "concurrency": {
+      "additionalProperties": {},
+      "properties": {
+        "account_id": {
+          "description": "Account the figures belong to.",
+          "type": "string"
+        },
+        "concurrent_calls": {
+          "description": "Calls in progress at this moment.",
+          "type": "number"
+        },
+        "max_concurrent": {
+          "description": "Maximum simultaneous calls the account may run.",
+          "type": "number"
+        },
+        "utilization_pct": {
+          "description": "concurrent_calls as a percentage of max_concurrent.",
+          "type": "number"
+        }
+      },
+      "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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful context beyond that: it clarifies the tool returns a count rather than a list and that it is useful as a pre-flight check before make_call batches, which is a real behavioral/workflow trait.

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: capability first, then the disambiguation from the list sibling, then the pre-batch usage tip. Every sentence earns its place and the most important scoping fact is front-loaded.

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?

Output schema exists, so return-value detail is not required, yet the description still names the key fields (concurrent_calls, max_concurrent, utilization_pct) at a glance. Combined with annotations and the sibling routing, an agent has everything needed to call this correctly.

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 there is nothing for the description to disambiguate; baseline is 4. The description correctly signals a parameterless account-level query rather than implying any filter inputs.

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 and resource ('Return this account's live call capacity') and even cites the underlying endpoint GET /concurrency. It explicitly distinguishes itself from the sibling list_live_calls by noting it is a count, not a list.

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 both an explicit alternative and the selecting condition ('to see which calls are live use list_live_calls'), plus a proactive usage rule: call it before a batch of make_call requests to avoid hitting the concurrency limit. Nothing is left 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