Skip to main content
Glama
jambonz

@jambonz/mcp-schema-server

Official
by jambonz
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_jambonz_schema

Get the JSON Schema for a jambonz verb or component to validate call flow configurations.

Instructions

Get the JSON Schema for a jambonz verb or component. Available: verb:agent, verb:alert, verb:answer, verb:conference, verb:config, verb:deepgram_s2s, verb:dequeue, verb:dial, verb:dialogflow, verb:dtmf, verb:dub, verb:elevenlabs_s2s, verb:enqueue, verb:gather, verb:google_s2s, verb:hangup, verb:leave, verb:listen, verb:llm, verb:message, verb:openai_s2s, verb:pause, verb:play, verb:redirect, verb:rest_dial, verb:room, verb:s2s, verb:say, verb:sip-decline, verb:sip-refer, verb:sip-request, verb:stream, verb:tag, verb:transcribe, verb:transfer, verb:ultravox_s2s, component:actionHook, component:actionHookDelayAction, component:amd, component:auth, component:bidirectionalAudio, component:fillerNoise, component:handoff, component:hangup, component:llm-base, component:recognizer-assemblyAiOptions, component:recognizer-awsOptions, component:recognizer-azureOptions, component:recognizer-customOptions, component:recognizer-deepgramOptions, component:recognizer-elevenlabsOptions, component:recognizer-gladiaOptions, component:recognizer-googleOptions, component:recognizer-houndifyOptions, component:recognizer-ibmOptions, component:recognizer-nvidiaOptions, component:recognizer-openaiOptions, component:recognizer-sonioxOptions, component:recognizer-speechmaticsOptions, component:recognizer-xaiOptions, component:recognizer, component:synthesizer, component:target, component:transferOptions, component:vad, callback:agent-turn, callback:amd, callback:call-status, callback:conference-status, callback:conference-wait, callback:conference, callback:dequeue, callback:dial-dtmf, callback:dial-hold, callback:dial-refer, callback:dial, callback:enqueue-wait, callback:enqueue, callback:gather-partial, callback:gather, callback:listen, callback:llm, callback:message, callback:play, callback:session-new, callback:session-reconnect, callback:session-redirect, callback:sip-refer-event, callback:sip-refer, callback:sip-request, callback:transcribe-translation, callback:transcribe, callback:transfer, callback:tts-streaming-event, callback:verb-status, guide:bridged-call-patterns, guide:conference-monitoring, guide:session-commands, guide:node-sdk

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesVerb or component name (e.g. "say", "gather", "recognizer", "guide:node-sdk")

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It only states the return type (JSON Schema) but does not disclose behavioral traits like whether it's read-only, requires authentication, or possible side effects. Minimal transparency beyond the operation's nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the purpose but then becomes verbose with a long list of items. While the list is useful, it could be better structured (e.g., grouped by type) for readability. The length exceeds what is necessary for a concise description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description does not detail the return value structure. However, 'JSON Schema' is self-explanatory for those familiar. The comprehensive input list provides completeness for parameter values, but missing output info slightly reduces overall completeness.

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 covers 100% of parameters, and description adds significant value by listing all valid values for the 'name' parameter (e.g., verbs, components, callbacks, guides), which goes beyond the schema's brief example. This enriches parameter understanding.

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?

The description clearly states 'Get the JSON Schema for a jambonz verb or component.' It identifies the specific verb-resource relationship and distinguishes the tool from siblings like get_sdk_example (examples) and list_jambonz_tools (tools listing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool over alternatives. Implicitly, if you need a schema, use this; but no mention of prerequisites or when not to use. Does not exclude alternative uses.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jambonz/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server