Skip to main content
Glama

Mapa Societario — Spanish Company Registry (BORME)

by es.mapasocietario

search_companies

Search Spanish companies by name in the BORME registry. Returns ranked matches (fuzzy — tolerant of typos) with status and a mapasocietario.es/empresa link to cite. A hit's name is always its CURRENT registered name; when the entity has been renamed, former_names lists its prior name(s) — a hit whose name differs from your query is not necessarily a wrong match, check former_names first. Use this first to resolve a company before get_company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-25, default 10).
queryYesCompany name or partial name.

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: fuzzy matching tolerant of typos, returns status and link, and explains the name/former_names logic in detail (current name always present, former_names lists prior names, a hit with different name is not necessarily wrong). This is exceptionally transparent for a search tool.

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?

Four concise sentences, each earning its place: purpose, return details, behavioral nuance, and usage recommendation. No fluff or redundancy. Front-loaded with the core action, making it easy to parse quickly.

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?

Given the tool has only 2 parameters, no output schema, and no annotations, the description covers the essential behavioral details (fuzzy matching, result structure with name, former_names, link, status) and provides usage context. No gaps are apparent for an agent to understand and invoke this tool correctly.

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

Parameters4/5

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

Schema coverage is 100% with clear descriptions, so baseline is 3. The description adds the critical nuance that the search is fuzzy and tolerant of typos, which enhances understanding of the query parameter beyond the schema. This justifies a 4.

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 'Search Spanish companies by name in the BORME registry', specifying the verb and resource. It distinguishes from sibling tool get_company by explicitly saying 'Use this first to resolve a company before get_company', making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes explicit guidance: 'Use this first to resolve a company before get_company', indicating when to use this tool versus an alternative. Also implies it is for initial fuzzy lookups and advises checking former_names if the name differs from the query, aiding correct usage.

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

All Mapa Societario — Spanish Company Registry (BORME) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get_company retrieves a single company's profile, get_company_network shows connections between companies, search_companies finds companies by name, and search_officers finds a person and their linked companies. The descriptions explicitly guide when to use each, eliminating ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get_company, get_company_network, search_companies, search_officers. The verbs 'get' and 'search' are used appropriately for retrieval vs. lookup, and the naming is predictable and clear.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of querying a Spanish company registry. The count covers the essential operations (search, details, network, officers) without being too few or excessive, each tool earns its place.

Completeness5/5

The tool set covers the core lifecycle of querying company registry data: searching for companies, retrieving detailed profiles, exploring corporate networks, and investigating officer connections. There are no obvious gaps for this read-only domain, and edge cases (former names, truncation, status) are well-handled.

Resources