Skip to main content
Glama
Sign In

OTP

by io.github.david-steel
OverviewDiscussionsAdmin

Approve a coaching action

approve_coaching_action

Approve one suggested action and carry it out -- creating the to-do, issue, measurable or meeting exactly as it was shown. The approving seat is taken from the caller's own session, never from arguments. Only ever call this after the person has seen the proposal and said yes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "intervention_id": "<intervention_id>"
    },
    "name": "approve_coaching_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
intervention_idYesThe intervention the person approved

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses key behavioral details beyond annotations: the approving seat comes from the caller's session, not arguments, and approval actually creates the promised artifact exactly as shown. Annotations already state this is not read-only, not destructive, and not open-world, so the remaining gap is minor.

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?

The description is two compact sentences and front-loads the core action before stating the session-derived seat and the human-approval precondition. Every sentence adds useful selection or invocation information.

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

Completeness4/5

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

For a one-parameter mutation with annotations and no output schema, the description covers purpose, side effect, authorization source, and human prerequisite. It does not describe the response or failure cases, but no major invocation-critical detail is missing.

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%, and the single parameter is already documented as the approved intervention. The description reinforces that the approving seat is never taken from arguments, but it does not add format or usage detail beyond the 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?

The description states a specific verb and resource: approve one suggested coaching action and carry it out by creating a to-do, issue, measurable, or meeting exactly as shown. It clearly distinguishes this approval operation from related sibling tools such as decline_coaching_action.

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?

It gives a strong precondition: only call after the person has seen the proposal and said yes. It does not explicitly mention the sibling alternative decline_coaching_action, but the usage context is clear enough for an agent to select correctly.

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

All OTP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources