Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

list_inbox

Read-only

Retrieve invoice files waiting in the inbox folder so an AP workflow can identify newly received invoices for processing.

Instructions

Invoice files waiting in the inbox folder.

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_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that, the description only adds the vague qualifier 'waiting' and does not clarify what state that corresponds to, whether results are paginated, or whether the inbox is shared across users. Low added value over structured data.

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 fragment with no filler or repetition. It is efficient, though the missing verb makes it feel more like a label than a lead sentence.

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 and there are no parameters, so the remaining burden is small and the description is close to sufficient. Still, for a listing tool the agent would benefit from knowing the meaning of the inbox state and how this list relates to the sibling invoice tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% and the empty object schema is self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase, not a verb+resource statement: it names the resource (invoice files) and the scope (waiting in the inbox folder), which does distinguish it from siblings like list_open_bills or list_vendors. But 'list_inbox' already implies this, so the text mostly restates the name with slightly more domain specificity and never states an action.

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, no prerequisite, and no reference to alternatives such as check_invoice or get_proposal. The word 'waiting' hints at pending/unprocessed invoices, but the agent must infer whether that means unopened, unapproved, or unposted.

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