eudr

Wallet balance and what it covers

eudr_account_usage

Idempotent

Report this organisation's credit balance, how many signed statements it will cover, and what has been spent. Checking plots, looking up references, assessing supplier gaps and reading traces cost nothing and are always available — only compiling a signed statement draws the balance down. Use this before starting a batch of compiles so the user is not surprised part-way through. The first call for an organisation writes: it opens the wallet, grants the welcome credits and records that grant as the opening ledger line. Every call after that only reads.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`charged_unit`	Yes
`organisation`	Yes
`credits_spent`	No
`free_of_charge`	Yes
`balance_credits`	Yes
`recent_activity`	No
`credits_received`	No
`analyses_remaining`	Yes
`credits_per_analysis`	Yes
`per_plot_pricing_from`	No
`credits_per_extra_plot`	No	Added for each plot after the first, from per_plot_pricing_from.
`welcome_credits_granted_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

addedOutput schema / properties / credits_per_extra_plot

Added value: +{
+  "description": "Added for each plot after the first, from per_plot_pricing_from.",
+  "type": "integer"
+}

addedOutput schema / properties / per_plot_pricing_from

Added value: +{
+  "format": "date",
+  "type": "string"
+}

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior3/5

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

The description carries an unusual and important disclosure that the annotations cannot: readOnlyHint=false is explained by "The first call for an organisation writes: it opens the wallet, grants the welcome credits and records that grant as the opening ledger line. Every call after that only reads," which also justifies idempotentHint=true and destructiveHint=false. Return format and any ledger detail are left to the output schema.

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 what is reported, then the cost model, then the first-call write nuance. Every sentence carries distinct information, though the free-vs-paid sentence and the write-behavior sentence are doing overlapping work that could be tightened slightly.

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?

An output schema exists, so return values need not be described. The description covers the cost model, the free/paid boundary, the one-time write on first call, and the recommended call timing — everything an agent needs to invoke it correctly and interpret when it mutates state.

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?

The tool takes zero parameters, so per the scoring baseline the schema imposes no documentation burden; there is nothing for the description to clarify about inputs. No credit or penalty beyond the baseline.

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 (report) and resource (this organisation's credit balance) and enumerates the exact contents: balance, number of signed statements covered, and spend. It is clearly distinguishable from siblings like eudr_export_statement or eudr_compliance_status 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 Guidelines5/5

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

Explicitly tells the agent when to call it ("Use this before starting a batch of compiles") and why (so the user is not surprised part-way through). It also draws the operational line between free operations (checking plots, lookups, gap assessment, traces) and the one operation that consumes balance, which is exactly the guidance needed to route between this tool and the compile-related siblings.

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

All eudr 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.