Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

propose_payment

Queues a scheduled payment for an open bill and submits it for human approval without paying it; specify bill ID, amount, and YYYY-MM-DD pay date.

Instructions

Queue a scheduled payment of an open bill for human approval. Does NOT pay. pay_date is YYYY-MM-DD. Uses the sandbox company's own bank account reference.

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": {
      "bill_id": "<bill_id>",
      "amount": "<amount>",
      "pay_date": "<pay_date>"
    },
    "name": "propose_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
bill_idYes
pay_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so mutability is known. The description adds real value by clarifying that nothing is actually paid and that the sandbox company's own bank account reference is used implicitly (no account parameter needed). It does not say whether repeated calls create duplicate proposals (relevant given idempotentHint=false), nor what approval state the proposal lands in.

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, front-loaded sentences with no filler; the most important constraint ('Does NOT pay') is placed early. The final sentence about the sandbox bank account reference is slightly tangential but still earns its place by explaining why no account parameter exists.

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 return values need no explanation, and the approval-workflow framing covers the main behavioral question. However, for a financial mutation with three fully required, undocumented parameters, the definition leaves amount formatting and duplicate-proposal behavior unaddressed.

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 description must carry parameter meaning and only does so for one of three: pay_date's YYYY-MM-DD format. bill_id is self-evident by name, but amount is typed as a bare string with no currency, format, or whether it must match the bill balance — a meaningful gap for a payment 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?

Specific verb and resource ('Queue a scheduled payment of an open bill'), with a scope qualifier ('for human approval') and an explicit negative boundary ('Does NOT pay'). This distinguishes it from the write-side sibling post_approved_proposal without needing to open 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 'for human approval' and 'Does NOT pay' phrasing clearly frames this as the pre-approval stage, implying the alternative is a separate posting step. It stops short of naming that alternative or stating preconditions (e.g. bill must be open, approval routing), so it is clear context rather than explicit when/when-not guidance.

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