Skip to main content
Glama
abhinav7895

Bolna MCP Server

by abhinav7895

bolna_patch_agent

Update specific fields of a Bolna agent, such as name, welcome message, webhook URL, or system prompt, without replacing the entire agent.

Instructions

Partially update specific fields of a Bolna agent (name, welcome message, webhook URL, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe unique ID of the agent to patch
agent_nameNoNew agent name
webhook_urlNoNew webhook URL or null to remove
system_promptNoNew system prompt
agent_welcome_messageNoNew welcome message
Behavior2/5

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

With no annotations, the description carries full burden. It states partial update (mutation) but does not disclose idempotency, permission requirements, side effects, or return behavior.

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?

Single sentence, front-loaded with key information, no unnecessary words.

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?

No output schema exists, and the description does not mention return values or expected output. For a mutation tool, this is a gap. Sibling tools exist but no comparative guidance provided.

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 coverage is 100%, so parameters are already documented. The description adds no new meaning beyond listing a few fields (name, welcome message, webhook URL).

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 tool partially updates specific fields of a Bolna agent, listing examples (name, welcome message, webhook URL). This distinguishes it from create, delete, get, and full-update tools among siblings.

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?

The description implies use for partial updates, but does not explicitly contrast with bolna_update_agent or provide when-not-to-use scenarios. No prerequisites or alternatives are mentioned.

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