Conecto

List or read bills

purchasing_list_bills

Read-onlyIdempotent

With bill_id: that bill in full (lines, payments, its PDF link, the books entry it posted). Otherwise bills by due date, filtered by status (open, partially_paid, paid, void; unpaid means open or partly paid; overdue means unpaid and past due), supplier, order, due on or before a date, or issued from-to. Free.

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

Input Schema

Name	Required	Description
`to`	No	YYYY-MM-DD
`from`	No	YYYY-MM-DD
`limit`	No
`order`	No	The order_id, or the order's number like "PO-0007".
`offset`	No
`status`	No
`bill_id`	No	The bill_id purchasing_create_bill returned.
`supplier`	No	A supplier_id, or the supplier's name.
`due_before`	No	YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely non-annotated context: what the detail view returns (lines, payments, the PDF link, the books entry it posted), the default ordering by due date, and that calls are free. It omits pagination behavior (default 50, max 200), which matters for a list tool.

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?

Dense and front-loaded — the bill_id mode leads, followed by the list filters — with no filler sentences. The trailing 'Free.' fragment is slightly abrupt but conveys useful information efficiently.

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?

With no output schema, the description covers return content for the detail mode and implies a filtered list for the other. For a 9-parameter list tool, the missing piece is pagination/limit behavior, which is only implicit in schema defaults.

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?

Adds real meaning beyond the 67%-covered schema: the status enum aliases are defined ('unpaid means open or partly paid; overdue means unpaid and past due'), and from/to are clarified as issue-date bounds ('issued from-to') rather than due dates, which the bare schema does not state. limit/offset remain unexplained, but their defaults and ranges are in the schema.

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 two distinct operations on a specific resource: a full single-bill read when bill_id is supplied, and a filtered list of bills otherwise. An agent can tell exactly what the tool does and which mode it gets without opening the 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?

The description clearly routes between the two modes (with bill_id vs. without) and enumerates the filters available for the list mode. It does not mention when to prefer this over nearby siblings such as purchasing_list_credits or purchasing_list_orders, so cross-tool selection is left to the names.

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

All Conecto tools Inspect

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

Need Help?