Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

post_approved_proposal

Idempotent

Write an approved proposal to the system of record only when enough reviewers have approved it and its payload is unchanged, preventing unapproved or altered postings.

Instructions

Write an APPROVED proposal to the system of record. Refuses unless enough people approved it and the payload is unchanged since they did.

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": {
      "proposal_id": "<proposal_id>"
    },
    "name": "post_approved_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds real behavioral detail beyond them: the call hard-fails unless a quorum has approved and the payload is byte-for-byte unchanged. That precondition is exactly the kind of thing an agent cannot infer from the schema. It does not say what the failure looks like or how 'enough people' is determined.

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 short sentences, no filler, with the core action front-loaded and the precondition immediately after. Nothing here could be cut without losing 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?

An output schema exists, so return values need no explanation, and the description covers the one non-obvious behavior (refusal conditions). What remains unstated — the error shape on refusal and where proposal_id comes from — is minor for a single-parameter write 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 0%, but there is only one parameter and 'proposal_id' is largely self-describing. The description adds no format, sourcing, or validation detail about the identifier, so it neither compensates for the coverage gap nor is it badly needed.

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?

States a specific verb and resource ('Write an APPROVED proposal') plus the target ('system of record'), which distinguishes it from the propose_* siblings that presumably create unapproved drafts. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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

Usage Guidelines3/5

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

The word 'APPROVED' plus the refusal condition implies this tool is only for proposals that already passed approval, which is usable context. However, it never tells the agent what to do instead when a proposal is not yet approved (e.g. use propose_bill) or how to verify approval state first.

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