Skip to main content
Glama

InvoiceQuick Free Invoice Generator

List currencies

list_currencies
Read-onlyIdempotent

Lists the currencies a free invoice can be issued in. Pass the code, for example USD, as currency_code to generate_free_invoice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by scoping the result set to free-invoice-eligible currencies and by indicating the values are codes rather than names, though it does not describe the response structure or ordering.

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 short sentences, both earning their place: the first defines scope, the second routes the agent to the next call. The purpose is front-loaded with no filler or repetition of the title.

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 zero-parameter read tool with no output schema, this is nearly complete — purpose, result semantics ('code, for example USD'), and downstream usage are all covered. The only small gap is that nothing describes the shape or size of the returned list (e.g. code/name pairs, ordering), which an agent might want when rendering results.

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?

With zero input parameters, the baseline is 4 and there is nothing in the schema to contradict. The description usefully pivots to the consumer side by naming currency_code on generate_free_invoice, telling an agent what to do with the output even though it takes no inputs itself.

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 and resource ('Lists the currencies') and narrows the scope precisely to those 'a free invoice can be issued in', which tells an agent exactly which universe of values this covers. The connection to generate_free_invoice makes its role in the sibling pair unmistakable.

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 effectively encodes the workflow: fetch codes here, then pass one as currency_code to generate_free_invoice. That makes the when-to-use condition clear without an explicit 'call this before X' imperative, and no exclusions are needed since there is only one sibling and one obvious use path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources