Skip to main content
Glama

regdata_spain_concursal

Search Spain's official public insolvency register by debtor name or NIF. Returns each party's role: debtor, disqualified, or insolvency administrator.

Instructions

Spain Registro Público Concursal Search. Search Spain's official public insolvency register (Registro Público Concursal) by debtor name or NIF. Returns each matching party with its role - debtor, disqualified, or insolvency administrator. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nifNoOne or more Spanish identifiers to look up. Used when search mode is "By identifier".
nameNoCompany name or person name to look up in the insolvency-publicity register (afectado). Leave empty when using a watchlist.
maxItemsNoOptional cap on billed dataset items returned.
watchlistNoA list of names to check in one run - the monitoring use case. Overrides "name". Each name costs one search.
maxResultsNoMaximum party records to export across all queries. The register serves results in pages, and the Actor pages through until it reaches this limit or runs out of matches. Set to 0 to export every match.
searchModeNoSearch by debtor/affected-party name, or by identifier (NIF/CIF/DNI/NIE).byName
identifierTypeNoType of identifier when searching by NIF.NIF
Behavior3/5

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

With no annotations, the description carries the burden. It explains the tool's purpose, mentions no API key requirement, and notes that advanced fields are accepted. It does not disclose rate limits, pagination details (though hinted in maxResults schema), or any other behavioral traits.

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 concise at four sentences, front-loading the purpose and key details without any wasted words. It efficiently communicates the tool's function and notes.

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?

Given no output schema, the description provides a useful high-level overview of the return type (matching parties with roles). It is complete enough for a search tool, though additional detail on the output structure would be beneficial.

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?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional meaning to individual parameters beyond the schema, but it does mention that advanced fields are accepted.

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 clearly states the tool searches Spain's official public insolvency register, specifying the registry name and the types of searches (by debtor name or NIF). It also distinguishes from siblings by country and register type.

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?

The description implies the tool is for Spanish insolvency searches and mentions alternative advanced fields via regdata_describe, but does not explicitly state when to use or not use this tool versus sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server