Skip to main content
Glama
abhinav7895

Bolna MCP Server

by abhinav7895

bolna_create_disposition

Create a call extraction disposition linked to a Bolna agent, defining how call transcripts are evaluated using an LLM with subjective or objective response options.

Instructions

Create a new call extraction disposition and link it to a Bolna agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the disposition
modelNoLLM model to use for evaluationgpt-4.1-mini
agent_idYesUUID of the agent this disposition will be linked to
categoryNoCategory grouping for the disposition (default: "General")General
questionYesThe prompt sent to the LLM to evaluate the transcript
is_objectiveNoEnable pre-defined value selection
is_subjectiveNoEnable free-text response
system_promptNoOptional system context for the evaluating LLM
subjective_typeNoFormat constraint for the free-text responsetext
objective_optionsNoRequired when is_objective is true
subjective_type_configNoRequired when subjective_type is 'regex'
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It fails to disclose any behavioral traits such as side effects (e.g., creating a linked resource), performance implications, or any constraints. The description merely states the action without further context.

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?

The description is a single, front-loaded sentence that clearly states the purpose. It is concise and free of unnecessary words, though it could be slightly expanded to improve completeness without losing brevity.

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

Completeness2/5

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

Given the complexity of the tool (11 parameters, nested objects, no output schema, no annotations), the description is insufficient. It does not explain the concept of a disposition, how the question/options interact, or what the agent linkage implies. This leaves the agent with significant gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all parameters. The description does not add any additional meaning beyond what is in the schema, which is the baseline expectation.

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 the action 'Create a new call extraction disposition' and the specific resource, and it explicitly mentions linking to a Bolna agent, which distinguishes it from sibling tools like bolna_bulk_create_dispositions and bolna_update_disposition.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context for when not to use it. For example, it doesn't indicate if the agent must exist before creating a disposition.

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/abhinav7895/bolna-mcp'

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