Skip to main content
Glama
Sign In

YESbusiness

by ch.yesbusiness
OverviewDiscussionsAdmin

Open customer invoices

list_open_receivables
Read-onlyIdempotent

The company's OPEN customer invoices (accounts receivable): every invoice synced from EZYinvoice that still carries a balance — fully open or partially paid — soonest due first, one page at a time. Use it for 'who still owes us', overdue follow-ups and the receivables total. Each item: number, customer_name, issue_date, due_date, currency (the invoice's own), total_cents and open_cents in that currency as integers in CENTS — divide by 100 — and status ('open' or 'partially_paid'). Overdue = due_date before today. itemsTotal is how many open invoices exist; nextPage is null on the last page. You cannot record a payment or send a reminder here.

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": {
      "company_id": "<company_id>"
    },
    "name": "list_open_receivables"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (default 1).
per_pageNoRows per page, 1-50 (default 25).
company_idYesThe company to work on — one of list_my_companies' company_id values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description still adds substantial context: ordering ('soonest due first'), pagination mechanics (itemsTotal, nextPage null on last page), the cents-as-integer convention, per-invoice currency, and the overdue definition. It also clarifies what is out of scope, which is exactly the kind of behavior an annotation cannot convey.

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?

Front-loaded with the resource definition, then use cases, then item shape and pagination, then scope limits — a logical progression with no filler. It runs long as a single dense paragraph and the field enumeration could be tighter, but every clause carries information.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of describing the return payload, and it does so completely: every field, its units, the status enum values, the pagination counters, and the overdue rule. Nothing an agent needs to call and interpret this tool is 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 100%, so page, per_page and company_id are already documented with defaults and ranges. The description reinforces pagination ('one page at a time') but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource combination ('OPEN customer invoices (accounts receivable)') and narrows the scope precisely: only invoices synced from EZYinvoice that still carry a balance, open or partially paid. An agent can distinguish this from list_bookings or get_account_statement without opening any 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?

Gives explicit use cases ('who still owes us', overdue follow-ups, receivables total) and an explicit boundary ('You cannot record a payment or send a reminder here'). It does not name a sibling tool to use for payment or statement needs, so routing to alternatives is left to inference.

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

All YESbusiness 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