Skip to main content
Glama

Spain company

run_es_companies
Read-onlyIdempotent

Get one company from the Spain registry (Registro Mercantil, Registradores de España open-data directory) by NIF/CIF or registry link: name, status (Vigente / Liquidada / Concurso), address, legal form, registry office and sheet number, IRUS and EUID identifiers, CNAE/NACE activity, website, special situation, administrators and officers with their roles, and other registry entries under the same NIF such as branches. 10 points per returned record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "run_es_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesNIF/CIF or registry URL. e.g. A15075062

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive. The description adds context the annotations cannot: the upstream data source and, importantly, the pricing model ('10 points per returned record'), which materially affects how an agent should budget calls. It does not describe not-found or error behavior.

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?

One front-loaded sentence leads with the action and source, then enumerates payload fields, then closes with the cost. The field enumeration is long but earns its place because no output schema exists. Slightly dense as a single sentence.

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 no output schema, the description carries the burden of telling the agent what comes back, and it does so thoroughly (identifiers, status values, officers, related entries). Cost is disclosed. Remaining gaps are failure modes and whether partial/fuzzy NIF input is tolerated.

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 100% and the single parameter's description already states 'NIF/CIF or registry URL. e.g. A15075062'. The description repeats that same dual-format acceptance without adding format rules, validation behavior, or tie-breaking. Baseline 3 is appropriate.

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 ('Get one company from the Spain registry') and names the exact source (Registro Mercantil / Registradores de España open-data directory), so an agent knows it is a single-record lookup. It never names the sibling run_es_companies_search, so the single-vs-list distinction is only implied by 'one company'.

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 identifier types accepted ('by NIF/CIF or registry link') imply the preconditions, but there is no explicit statement of when to use this instead of run_es_companies_search or what to do if only a company name is known. Usage is inferable rather than stated.

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