Skip to main content
Glama

get_proposal

Read-only

Read the open proposal of the automatic planner, if any: why it needs approval and each block change (before and after, reason codes). The user accepts or rejects it in the week view, or a caller allowed to apply changes with decide_proposal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description adds genuinely new behavior: the proposal may not exist, its payload includes before/after diffs and reason codes, and this tool never applies changes. It does not cover freshness or whether the proposal can change between reads, which keeps it short of 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 tight sentences with the resource and condition front-loaded and the delegation to decide_proposal last. The clause about the user accepting or rejecting in the week view is slightly tangential to an agent's decision but still costs only one phrase.

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?

With no output schema, the description carries the burden of describing the return value, and it does so at a useful level of abstraction (approval reasons, per-block changes, reason codes). The absence of an empty-state hint beyond 'if any' is a minor gap for an otherwise simple, self-contained tool.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond confirming the no-argument read. Baseline 4 applies for a 0-parameter tool.

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 a specific verb (read) with a specific resource (the open proposal of the automatic planner) and states the scope constraint 'if any'. It also previews the content shape (why approval is needed, per-block before/after with reason codes), which lets an agent distinguish it from decide_proposal without opening any 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?

Explicitly routes the apply path to decide_proposal and notes the human path (accept/reject in the week view), which is real when-to-use guidance. What is missing is an explicit statement of when to call this versus reading the schedule directly (get_schedule), but the guidance present is clear and actionable.

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