Skip to main content
Glama

MiCA e-money token register

mica_stablecoin_register
Read-only

Issuers of e-money tokens (EU-authorized stablecoins such as EURC and USDC) on ESMA's interim MiCA register: legal and commercial name, home member state, supervisor, type of institution and white papers. Optionally filter by name.

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

Input Schema

NameRequiredDescriptionDefault
queryNoPart of an issuer's legal or commercial name, e.g. Circle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context the annotations do not: the data source (ESMA interim MiCA register), the scope (EU-authorized e-money token issuers), and the specific fields present in each record in lieu of an 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?

Two tight sentences with no filler: the resource and contents come first, the filtering behavior second. The only mild inefficiency is that 'Optionally filter by name' largely restates the schema's own wording.

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 simple single-parameter read tool, the description is sufficient: it identifies the source, the scope of records, and the fields returned in the absence of an output schema. Minor omissions are whether the interim register is exhaustive/current and whether results are paginated or capped.

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 coverage is 100% and the single parameter is fully documented in the schema, including that it matches part of a legal or commercial name. The description's 'Optionally filter by name' confirms optionality but adds no matching semantics beyond the schema.

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 resource (issuers of e-money tokens on ESMA's interim MiCA register) and enumerates the fields returned, which clearly separates it from rate/network-fee siblings. It lacks an explicit verb (list/retrieve), so the operation type must be inferred from the readOnly annotation and the shape of the output fields.

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?

Usage is only implied: an agent can infer it should call this when it needs MiCA register issuer data, and the description notes filtering is optional. There is no explicit statement of when to prefer this over another source, nor any exclusion or prerequisite.

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