Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

get_proposal

Read-only

Retrieves the current status of an accounts payable proposal by proposal ID, returning pending, approved, rejected, executed, or failed.

Instructions

Status of a proposal: pending, approved, rejected, executed or failed.

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": "get_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

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed-world, non-mutating read. The description adds the set of possible status outcomes, which is real behavioral context about what the call can reveal, but it says nothing about behavior when the proposal_id does not exist or when a status is still in flux.

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?

A single short sentence with the resource and the value domain front-loaded; nothing is redundant or padded. It is terse to the point of under-specification, but no sentence fails to earn its place.

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

Completeness3/5

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

An output schema exists, so the description need not describe return values, and annotations cover the safety profile. What is still missing for a one-parameter lookup is how to obtain a valid proposal_id and what happens on an unknown ID, which keeps this at minimum-viable rather than complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the single required proposal_id parameter is documented nowhere. The description does not explain where the identifier comes from, its expected format, or whether it is the same ID returned by the propose_bill/propose_payment siblings, leaving a genuine gap the description should have closed.

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?

The description names a specific resource (a proposal) and states exactly what is returned: its status, enumerated as pending, approved, rejected, executed or failed. That is enough to separate it from resource-different siblings like get_purchase_order or get_audit_trail, though it never explicitly frames the retrieval action or contrasts it with any alternative.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing about when an agent should check proposal status versus polling a list tool such as list_inbox, and no mention of prerequisites like needing a proposal_id obtained from a prior propose_* call. Usage must be inferred entirely from the name.

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