Skip to main content
Glama

vocametrix_approve_therapy_plan

Approve, reject, or request modifications to a generated therapy plan. Approval locks and delivers the plan; rejection discards it; modifications require feedback to regenerate.

Instructions

Human-in-the-loop approval gate for generated therapy plans. Actions: 'approve' (locks and delivers plan), 'reject' (discards), 'modify' (requires feedback, re-generates). This action is irreversible — once approved, the plan is sent for delivery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID from vocametrix_generate_therapy_plan
actionYesApproval decision
feedbackNoRequired when action = 'modify': describe the changes needed
Behavior4/5

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

Discloses irreversible approval, locking and delivery, rejection, and modification with feedback. No annotations provided, so description carries burden. Adequately covers behavior for a simple workflow gate.

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?

Two sentences with bulleted actions. No unnecessary words. Efficiently conveys essential information.

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, and description does not explain return value or result format. For a simple approval action, this is a mild gap. Otherwise complete for the core function.

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 has 100% description coverage. Description adds that feedback is required for modify, which is already implied by schema enum and conditional field. Minimal additional value beyond schema.

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?

Description clearly states it is an approval gate for generated therapy plans, listing three distinct actions with effects. This distinguishes it from sibling tools like generate_therapy_plan and get_therapy_status.

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

Usage Guidelines4/5

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

Implies usage after generating a therapy plan. Mentions irreversibility of approve. Lacks explicit when-not-to-use or alternative tools, but context is reasonably clear.

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/pmarmaroli/vocametrix-mcp'

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