Skip to main content
Glama

amberflo

by io.usefulapi
OverviewDiscussionsAdmin

Get customer invoice

amberflo_get_customer_invoice
Read-only

Get a single customer invoice: the CURRENT open invoice (latest=true, default) or a SPECIFIC past invoice by product_plan_id + year + month + day. API: GET /payments/billing/customer-product-invoice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoDay of month of a specific past invoice.
yearNoYear of a specific past invoice.
monthNoMonth (1-12) of a specific past invoice.
latestNoFetch the current open invoice. Default true. Ignored when a specific invoice is addressed.
from_cacheNoUse cached invoice (faster). Default true.
product_idNoProduct id. Default "1".
customer_idYesThe Amberflo customerId.
product_plan_idNoProduct plan id of a specific past invoice (with year/month/day).
with_payment_statusNoInclude payment status. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true. The description adds the API endpoint and the two operational modes (current vs specific), providing useful behavioral context beyond annotations.

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?

Two sentences, front-loaded with main action, zero wasted words. Efficient and clear.

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?

No output schema, but description covers all input modes and defaults. Could mention return object structure, but given simplicity, it is adequately complete.

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?

Schema coverage is 100% but description groups parameters logically (latest for current, product_plan_id+year+month+day for specific), adding meaning beyond individual descriptions.

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 clearly states the tool gets a single customer invoice, specifying two modes: current open invoice (latest=true) or specific past invoice by product_plan_id+year+month+day. This distinguishes it from sibling list tool.

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 description implies when to use each mode (current vs specific) but does not explicitly compare with alternatives like list_customer_invoices. Context is clear but not directive.

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

All amberflo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources