Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

list_open_bills

Read-only

Retrieve unpaid bills and their outstanding balances, optionally filtered to a single vendor, to support accounts payable review and payment planning.

Instructions

List bills with an unpaid balance, optionally for one vendor.

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

Input Schema

NameRequiredDescriptionDefault
vendor_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description usefully adds the implicit filter that only bills with an unpaid balance are returned. However, it says nothing about ordering, pagination, or result size limits, which are relevant for a list operation. With annotations carrying the safety burden, a 3 is appropriate.

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?

A single sentence with the resource and the key scoping constraint front-loaded and zero filler. Nothing could be removed without losing meaning.

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?

For a one-optional-parameter read tool with an output schema, the description covers purpose, scope, and the optional filter, which is enough to call it correctly. Only minor behavioral details like ordering or empty-result behavior are missing.

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 coverage is 0%, so the description must carry the parameter meaning. It does convey two important facts the schema does not: the vendor filter is optional and it narrows rather than widens results. It adds no format detail for the vendor_id string and no hint about what happens when the filter matches nothing.

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 verb and resource ("List bills") plus a defining scope condition ("with an unpaid balance"), which distinguishes it from the sibling list_purchase_orders and list_vendors tools by resource type. It stops short of naming any sibling explicitly, so it lands at a clear 4 rather than 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?

"Optionally for one vendor" implies when the parameter is used but gives no explicit guidance on when to choose this tool over alternatives, no prerequisites, and no exclusions. Usage must be inferred from the resource and filter semantics rather than stated.

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