Skip to main content
Glama

get_proposal

Get the current proposal content for an edit. Returns full markdown for context plus the proposal summary and full-proposal link. Show a short summary and link in chat; show full markdown only if requested. Approval can happen in chat using set_proposal_status.

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": {
      "workspaceId": "<workspaceId>",
      "editId": "<editId>"
    },
    "name": "get_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
editIdYesThe edit ID
proposalIdNoSpecific proposal ID
workspaceIdYesThe workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return payload shape (markdown plus summary plus link) and how to present it, but says nothing about what happens when the optional proposalId is omitted, whether the call is strictly read-only, or error behavior when no proposal exists.

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?

Three short sentences, return content front-loaded before presentation guidance and the approval hand-off. Slight redundancy between the return-value sentence and the display instruction, but no filler.

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?

No output schema exists, so the description rightly explains what is returned and how to render it, which covers the main gap. Only the semantics of the optional proposalId and failure modes remain unaddressed for a simple three-parameter read tool.

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 description coverage is 100%, so the schema already documents all three parameters and the baseline is 3. The description adds no meaning about the optional proposalId, which is the one parameter whose omission behavior an agent would want explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Get the current proposal content for an edit', and it states exactly what comes back (full markdown, summary, full-proposal link). It implicitly separates itself from save_proposal/update_proposal by being a read of the current proposal, though it never names those siblings explicitly.

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?

Gives concrete presentation guidance ('Show a short summary and link in chat; show full markdown only if requested') and routes approval work to set_proposal_status. It lacks explicit when-not guidance versus get_edit or update_proposal, but the usage context is clear.

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.