Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Load a Vobiz skill

get_vobiz_skill
Read-only

Return bundled Vobiz Agent Skill Markdown playbooks with endpoints, request shapes, VobizXML rules, and pitfalls to read before building; optionally fetch one section by heading.

Instructions

Return the Markdown text of one bundled Vobiz Agent Skill: a documentation playbook with endpoints, request shapes, VobizXML rules and pitfalls to read before building something on Vobiz. Pass section to get one ## section instead of the whole text; an unknown section fails with not_found and the error lists the available headings. It returns text and performs nothing on the account; use list_vobiz_skills to see which skills and sections exist, and the operational tools for live actions. Local lookup, no Vobiz API request.

Input Schema

NameRequiredDescriptionDefault
nameYesSkill name from list_vobiz_skills, e.g. vobiz-voice-calls.
sectionNoOptional `##` heading to return instead of the whole skill (case-insensitive prefix match on the headings list_vobiz_skills shows).

Output Schema

NameRequiredDescriptionDefault
okNotrue on success; false (with error and message) when the tool failed.
nameNoThe skill that was loaded.
filesNoOther files shipped with the skill (relative paths such as references/*.md); present only for the whole skill.
sectionNoThe matched heading, present only when section was passed.
descriptionNoIts one-line description.
instructionsNoThe skill text (whole body, or the one section) as Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.3
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "vobiz-ai-voice-agents",
-  "vobiz-api",
-  "vobiz-applications-endpoints",
-  "vobiz-audio-streams",
-  "vobiz-cdr",
-  "vobiz-forward-deployed-engineer",
-  "vobiz-partner-api",
-  "vobiz-phone-numbers",
-  "vobiz-plivo-migration",
-  "vobiz-sip-trunking",
-  "vobiz-sms",
-  "vobiz-sub-accounts",
-  "vobiz-voice-calls",
-  "vobiz-voice-xml",
-  "vobiz-whatsapp"
-]New value: +[
+  "vobiz-ai-voice-agents",
+  "vobiz-api",
+  "vobiz-applications-endpoints",
+  "vobiz-audio-streams",
+  "vobiz-campaign-planner",
+  "vobiz-cdr",
+  "vobiz-forward-deployed-engineer",
+  "vobiz-partner-api",
+  "vobiz-phone-numbers",
+  "vobiz-plivo-migration",
+  "vobiz-reports",
+  "vobiz-sip-trunking",
+  "vobiz-sms",
+  "vobiz-sub-accounts",
+  "vobiz-voice-calls",
+  "vobiz-voice-xml",
+  "vobiz-whatsapp"
+]
  2. Changed2 schema fields changedv1.4.2
    • changedInput schema / properties / section / description
      Previous value: -"Optional `##` heading to return instead of the whole skill (case-insensitive prefix match)."New value: +"Optional `##` heading to return instead of the whole skill (case-insensitive prefix match on the headings list_vobiz_skills shows)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "description": {
+      "description": "Its one-line description.",
+      "type": "string"
+    },
+    "files": {
+      "description": "Other files shipped with the skill (relative paths such as references/*.md); present only for the whole skill.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "instructions": {
+      "description": "The skill text (whole body, or the one section) as Markdown.",
+      "type": "string"
+    },
+    "name": {
+      "description": "The skill that was loaded.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "true on success; false (with error and message) when the tool failed.",
+      "type": "boolean"
+    },
+    "section": {
+      "description": "The matched heading, present only when section was passed.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observedv1.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description reinforces this with 'returns text and performs nothing on the account' and 'Local lookup, no Vobiz API request', which is valuable context about latency and side effects. The failure semantics of an unknown section are also disclosed. An output schema exists, so omitting return-shape detail is acceptable.

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?

Dense and front-loaded: the core action comes first, then the section modifier, then safety and routing. It is slightly longer than strictly necessary, stacking several clauses into one paragraph, but every sentence carries information.

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?

With an output schema covering return values and annotations covering the safety profile, the description fills the remaining gaps: what the content is, how to discover names, what happens on a bad section, and that no API call occurs. Nothing an agent needs to invoke 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?

Schema coverage is 100% and the enum already lists all skill names, so the baseline would be 3. The description adds meaning beyond the schema by explaining that an unknown section fails with not_found and that the error enumerates available headings, which materially helps callers recover.

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: returns the Markdown text of one bundled Vobiz Agent Skill, described concretely as a documentation playbook with endpoints, request shapes, VobizXML rules and pitfalls. It is immediately distinguishable from list_vobiz_skills (enumeration) and the operational tools (live actions).

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 says to read it before building on Vobiz, names list_vobiz_skills as the way to discover skills and sections, and routes live actions to the operational tools. The section behavior and its not_found failure mode are spelled 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