Eudigo – EUDI Wallet index

List EUDI Wallets by country

list_countries

Read-onlyIdempotent

Overview of the EUDI Wallet in all 27 EU member states: wallet name, status and short note.

    Status meaning: certified (listed as certified EUDI Wallet), live (precursor app with digital credentials
    in operation), pilot (tests with real users or public test version), upgrade (existing government app
    officially set to become the EUDI Wallet), announced (project known, no public app), unclear.
    Optionally filter by status. Use get_country for sources and history of one country.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No		en
`status`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, and closed-world nature of the tool. The description adds useful behavioral context by explaining the output fields and defining each status value, which is important for interpreting results correctly.

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?

The description is front-loaded with the tool's scope and is tightly structured. The status definitions are necessary for correct interpretation, and nothing is wasted.

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 an output schema and rich annotations present, the description does not need to repeat safety or return-value details. It is largely complete for a two-parameter read-only listing tool, but the missing explanation of the lang parameter is a small gap.

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 0%, so the description must carry parameter meaning. It explains the status filter and each status value well, but it says nothing about the lang parameter, leaving one of the two parameters underexplained in both the schema and the description.

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?

The description states a specific verb and resource: an overview of the EUDI Wallet across all 27 EU member states, with wallet name, status, and short note. It explicitly distinguishes itself from get_country by positioning that sibling as the source for one country's sources and history.

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?

It states the optional status filter and names get_country as the alternative for per-country sources and history. The condition for choosing between the overview and the single-country tool is clear, though the guidance stops short of a fully explicit when-to-use/when-not-to-use statement.

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

All Eudigo – EUDI Wallet index 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?