Skip to main content
Glama

thanaton_list_invoices

Retrieves billing history, invoices, transaction receipts, and payment ledger entries, with an optional organization slug filter for scoped results.

Instructions

Retrieve billing history, invoices, transaction receipts, and payment ledger entries.

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

Input Schema

NameRequiredDescriptionDefault
org_slugNoOptional organization slug filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. "Retrieve" implies a read, but it doesn't say whether the call is org-scoped by default, whether results are paginated or truncated, whether one call returns all four data types or only some, or what permissions are required.

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?

One front-loaded sentence with no filler. The only weakness is that the comma-separated enumeration is slightly ambiguous about whether all listed items are returned together or represent separate record kinds.

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?

For a simple one-optional-param list tool with no output schema, the definition is minimally sufficient to select and call it. It still leaves the default scope (all orgs vs one), result ordering, and pagination behavior unexplained, which matters for a billing-history endpoint.

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 description coverage is 100% for the single optional org_slug parameter, so the schema already explains it. The description never mentions the filter, but per the baseline rule a 3 is appropriate when the schema does the explaining.

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?

States a specific verb ("Retrieve") and enumerates the resources it covers (billing history, invoices, receipts, ledger entries), so the agent knows this is the billing-data read tool. It does not differentiate itself from any sibling, but no billing-related sibling exists, so the gap is minor.

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 mention of when to prefer a different tool, and no statement of prerequisites or scope limits. The agent must infer that this is the tool to call whenever invoice or payment data is needed.

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

Deploy Server

Other Tools