Skip to main content
Glama
vobiz-ai

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Vobiz skills

list_vobiz_skills
Read-only

Lists bundled Vobiz Agent Skills documentation playbooks, showing each skill's name, summary, URI, and headings so you can read build guidance before coding integrations.

Instructions

List the Vobiz Agent Skills bundled with this server: documentation playbooks (Markdown reference text synced from the Vobiz docs) that explain how to build on each Vobiz product with the REST API and VobizXML. Each entry gives the skill's name, one-line description, resource URI and its ## section headings; read the text with get_vobiz_skill before planning a multi-step task or writing integration code. The skills are reading material only: a skill about a product does not mean this server has operational tools for it, and the live-account tools are the other tools in this list. Local lookup, no Vobiz API request.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okNotrue on success; false (with error and message) when the tool failed.
countNoNumber of bundled skills.
skillsNoThe bundled skills, sorted by name.

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": {
+    "count": {
+      "description": "Number of bundled skills.",
+      "type": "number"
+    },
+    "ok": {
+      "description": "true on success; false (with error and message) when the tool failed.",
+      "type": "boolean"
+    },
+    "skills": {
+      "description": "The bundled skills, sorted by name.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "description": {
+            "description": "One line on what the skill covers.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Skill name to pass to get_vobiz_skill, e.g. vobiz-voice-calls.",
+            "type": "string"
+          },
+          "sections": {
+            "description": "The skill's `##` headings, usable as the section argument of get_vobiz_skill.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "uri": {
+            "description": "Resource URI of the same text (vobiz://skills/<name>) for clients that read resources.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. 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, and the description reinforces this with 'Local lookup, no Vobiz API request,' plus the useful caveat that skills are reading material only. It stops short of covering pagination or output shape, but the safety/scope profile is well covered.

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?

One dense paragraph, front-loaded with what the tool lists before moving to the get_vobiz_skill handoff and the reading-material caveat. Every clause carries information, though the paragraph is long enough that a reader must work through it rather than scan.

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?

For a zero-parameter local listing tool with an output schema, the description covers purpose, the read-with-sibling workflow, and the conceptual caveat that documentation presence is not operational capability. Nothing an agent needs to decide whether to call it 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. The description instead clarifies what each returned entry contains (name, one-line description, resource URI, ## section headings), which is helpful context even though output schema exists.

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 ('List the Vobiz Agent Skills bundled with this server') and immediately defines what a skill actually is (Markdown documentation playbooks synced from Vobiz docs). It also distinguishes the listing tool from the sibling that reads the content, get_vobiz_skill.

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 tells the agent when to go further: 'read the text with get_vobiz_skill before planning a multi-step task or writing integration code.' It also draws a when-not boundary by warning that a skill's existence does not mean the server has operational tools for that product, and that live-account work lives in the other tools.

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