Skip to main content
Glama

decide_proposal

Accept or reject the planner's open proposal (see get_proposal). Accepting applies its block changes; if the calendar changed in the meantime, the planner runs afresh instead (status stale).

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": {
      "decision": "<decision>"
    },
    "name": "decide_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYes
proposalIdNoThe proposal to decide; default the open one. Pass it to avoid deciding a newer one by accident.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say readOnly=false and destructive=false; the description adds real behavioral context by disclosing that accepting applies block changes and that a concurrently modified calendar causes a stale status and a fresh planner run. It does not describe what rejecting does or what the response returns, which keeps it below a 5.

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?

Two dense sentences, front-loaded with the action, then the accept semantics and the stale edge case. The parenthetical '(status stale)' is terse but functional; nothing is redundant.

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 two-parameter mutation tool with no output schema and minimal annotations, the description covers the primary effect and the main race-condition outcome. Remaining gaps (reject semantics, response shape) are noticeable but not blocking for correct invocation.

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 50%, and the one nontrivial parameter (proposalId, with its 'avoid deciding a newer one by accident' caveat) is documented in the schema itself. The description's 'Accept or reject' wording mirrors the decision enum but adds no new semantics beyond that.

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?

Uses specific verbs ('accept or reject') on a specific resource ('the planner's open proposal') and explicitly routes to the sibling get_proposal for inspection. An agent can distinguish this from get_proposal or replan without opening either schema.

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?

The '(see get_proposal)' pointer establishes the read-then-decide workflow, and the description explains the consequence of choosing 'accept'. It stops short of stating when to choose 'reject' or when to use replan instead, so the exclusion guidance is implicit rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources