eu-reg-mcp

search_micar_register

Read-onlyIdempotent

Search the ESMA interim MiCAR register by entity name or LEI to find CASPs, EMT/ART issuers, and other entities. Filter by register or member state and check source files plus snapshot freshness.

Instructions

Search the ESMA interim MiCAR register by entity name or LEI.

query: entity-name substring (case- and accent-insensitive) or an exact LEI. Each result carries its entry_id and the ESMA source file; the response states the snapshot date, data_age_days and a stale flag. register_slug: all | other-wp | emt-wp | art-wp | casps | ncasp. member_state: optional two-letter code (DE, IE, MT, ...). offset: skip this many matches (results come 25 at a time; see truncated).

Input Schema

Name	Required	Default
`query`	Yes
`offset`	No
`member_state`	No
`register_slug`	No	all

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Oct 18, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

addedInput schema / properties / register_slug / enum

Added value: +[
+  "all",
+  "other-wp",
+  "emt-wp",
+  "art-wp",
+  "casps",
+  "ncasp"
+]

First observedv0.1.0Jul 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the bar is lower. The description goes beyond them with genuinely useful operational context: results come 25 at a time with a truncated flag, and responses carry entry_id, source file, snapshot date, data_age_days and a stale flag.

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 the core purpose in the first line, then one line per parameter with no filler. Slightly clunky line-wrapping that splits a sentence across lines, but nothing is wasted.

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?

Complete for a filtered search: an agent knows the key, the filters, the paging model and the freshness signals. Return-value detail beyond the output schema is a bonus rather than a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry the full load, and it does: query is documented as case- and accent-insensitive substring or exact LEI, register_slug's enum values are listed with meaning, member_state is given as a two-letter code with examples, and offset is tied to the 25-per-page/truncated paging model.

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?

States a specific verb and resource with scope: 'Search the ESMA interim MiCAR register by entity name or LEI.' The name/LEI lookup key clearly separates it from sibling tools like micar_register_summary and micar_register_changes, though it never names those alternatives explicitly.

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 implied by the query semantics (entity-name substring or exact LEI), but there is no statement of when to reach for this tool over micar_register_summary or micar_register_changes, and no exclusions or prerequisites.

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

Deploy Server