Skip to main content
Glama

List payment methods

crunch_list_payment_methods
Read-only

Lists available payment methods, such as EFT, CASH, or DIRECTORS_EXPENSES, so you can choose the correct name when recording expense or invoice payments.

Instructions

List payment methods (for example EFT, CASH, DIRECTORS_EXPENSES) for recording expense payments or invoice payments. Use name as the payment method.

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

Input Schema

NameRequiredDescriptionDefault
forNoExpense payments (default) or invoice (customer) payments
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value
directionNoFor invoices: the payment direction as Crunch names it (default INCOMING, money received from customers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/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 without prose. The description adds one genuinely useful behavioral note — that the returned `name` field is the value to use as the payment method — but says nothing about pagination, default limits, or ordering for what is a list endpoint.

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?

Two short sentences, purpose front-loaded, with the usage hint on how to consume the result placed second. No filler or repetition of the title, though the final sentence is telegraphic enough that its meaning depends on the earlier examples.

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?

For a read-only, zero-required-parameter list tool with a fully documented schema and no output schema, this covers purpose, intended use, and how to use the returned value. The only real gap is pagination/limit behavior, which is minor given annotations already signal a safe, non-open-world read.

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%, so all five optional parameters are already self-documenting, including the `for` enum and the `direction` default. The description adds no parameter-level detail beyond what the schema provides, so the baseline of 3 applies.

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?

The description names a specific verb and resource (list payment methods) and gives concrete example values (EFT, CASH, DIRECTORS_EXPENSES), which makes the domain immediately legible. It does not explicitly distinguish itself from sibling list tools, but the resource name is distinct enough that confusion is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the downstream purpose — "for recording expense payments or invoice payments" — which implies this is reference data to fetch before creating a payment. There is no explicit when-not guidance or named alternative, and the choice between `for: expenses` and `for: invoices` is left to the schema description.

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