Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

propose_bill

Drafts a bill from an invoice and queues it for human approval without posting, so payment remains pending review.

Instructions

Draft a bill from an invoice and queue it for human approval. Does NOT post it.

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": "propose_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filenameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, and idempotent=false, so the safety baseline is set. The description adds meaningful workflow behavior beyond annotations: it creates a draft, queues it for human approval, and explicitly does not post it. It does not cover auth requirements or duplicate-call behavior, but it discloses the key side effect and approval gate.

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?

The definition is two short sentences, front-loaded with the core action and immediately followed by the critical constraint. There is no filler, and the negative constraint is placed where it prevents a costly mistake.

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

Completeness2/5

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

The output schema means return values need not be described, and the annotations cover the safety profile. However, with 0% parameter coverage and no parameter explanation in the description, an agent cannot determine how to supply the invoice text or filename or why both are optional. For a mutation tool that queues a bill for approval, that is a significant completeness gap.

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

Parameters1/5

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

Schema description coverage is 0% for two optional nullable parameters, text and filename, and the description never explains what they represent, how they relate to the invoice, or what happens when they are omitted. The phrase 'from an invoice' gives only a vague hint and does not map meaning to either parameter.

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?

The description states a specific verb and resource: 'Draft a bill from an invoice and queue it for human approval.' The explicit 'Does NOT post it' clearly separates this tool from posting-related siblings such as post_approved_proposal.

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?

It gives clear usage context: create a draft bill from an invoice and route it for human approval. The negative constraint 'Does NOT post it' provides a useful when-not boundary, though it does not explicitly name the alternative tool for posting.

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