ENTIA Entity Verification

Get Competitors

get_competitors

Read-onlyIdempotent

PAID (requires BUILD plan or higher, from €99/month). Use when the user asks who competes with a business in a sector and Spanish city. Find real competitors in the same sector and city. Ranked entities with identity + location + sector matching. Spain only on the public surface. sector is a closed vocabulary — see the enum; aliases such as abogados (the slug ENTIA uses in its own Entia Home URLs) resolve to their canonical slug.

Input Schema

Name	Required	Description
`city`	Yes	City name in Spain (Madrid, Barcelona, Valencia, Sevilla, Bilbao)
`limit`	No	Max results (1-30)
`sector`	Yes	ENTIA sector slug. Canonical: dental, legal, estetica, psicologia, medicos, talleres, veterinarios, reformas, inmobiliarias, asesorias, gimnasios… Aliases (abogados, salud, dentist, beautysalon…) resolve to a canonical slug and the response declares the translation in _meta.sector_resolved_from.

Output Schema

Name	Required	Description
`city`	No
`_meta`	No	Carries sector_resolved_from / sector_resolved_to
`count`	No
`sector`	No	Canonical slug actually used after alias resolution
`country`	No
`competitors`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Ranked competitors in the same sector and city. Spain only on the public surface.",
+  "properties": {
+    "_meta": {
+      "description": "Carries sector_resolved_from / sector_resolved_to",
+      "type": "object"
+    },
+    "city": {
+      "type": "string"
+    },
+    "competitors": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "country": {
+      "type": "string"
+    },
+    "sector": {
+      "description": "Canonical slug actually used after alias resolution",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed7 schema fields changedAug 18, 2026

changedInput schema / properties / city / description

Previous value: -"City name (Madrid, Barcelona, London, Paris)"New value: +"City name in Spain (Madrid, Barcelona, Valencia, Sevilla, Bilbao)"

addedInput schema / properties / limit / description
```
Added value: +"Max results (1-30)"
```
changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +30
```

changedInput schema / properties / sector / description

Previous value: -"ENTIA sector slug (estetica, dental, psicologia, legal, …)"New value: +"ENTIA sector slug. Canonical: dental, legal, estetica, psicologia, medicos, talleres, veterinarios, reformas, inmobiliarias, asesorias, gimnasios… Aliases (abogados, salud, dentist, beautysalon…) resolve to a canonical slug and the response declares the translation in _meta.sector_resolved_from."

addedInput schema / properties / sector / enum

Added value: +[
+  "abogados",
+  "accountingservice",
+  "asesoria",
+  "asesorias",
+  "attorney",
+  "automocion",
+  "automotivebusiness",
+  "autorepair",
+  "barberia",
+  "barberias",
+  "beautysalon",
+  "belleza",
+  "clinicas",
+  "construccion",
+  "consultoria",
+  "dental",
+  "dentist",
+  "dentista",
+  "ecommerce",
+  "educacion",
+  "energia",
+  "estetica",
+  "exercisegym",
+  "farmacia",
+  "farmacias",
+  "financial",
+  "financialservice",
+  "fisio",
+  "fisioterapia",
+  "foodestablishment",
+  "generalcontractor",
+  "gestion",
+  "gestoria",
+  "gestorias",
+  "gimnasio",
+  "gimnasios",
+  "hairsalon",
+  "healthandbeautybusiness",
+  "healthcare",
+  "healthclub",
+  "homeandconstructionbusiness",
+  "hospital",
+  "hospitality",
+  "inmobiliaria",
+  "inmobiliarias",
+  "insurance",
+  "insuranceagency",
+  "legal",
+  "legalservice",
+  "medicalbusiness",
+  "medicalclinic",
+  "medico",
+  "medicos",
+  "nutricion",
+  "optica",
+  "opticas",
+  "optician",
+  "peluqueria",
+  "peluquerias",
+  "pharmacy",
+  "physician",
+  "physiotherapyclinic",
+  "podologia",
+  "psicologia",
+  "psychologist",
+  "realestate",
+  "realestateagent",
+  "reformas",
+  "restauracion",
+  "restaurant",
+  "restaurantes",
+  "rrhh",
+  "saas",
+  "salud",
+  "security",
+  "seguros",
+  "sportsactivitylocation",
+  "taller",
+  "talleres",
+  "telecom",
+  "turismo",
+  "veterinario",
+  "veterinarios",
+  "veterinarycare"
+]

removedInput schema / properties / sector / maxLength
```
Removed value: -50
```
removedInput schema / properties / sector / minLength
```
Removed value: -2
```

Changed5 schema fields changedMay 26, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / city / description

Previous value: -"City name in the target country (e.g. Madrid, Barcelona, London, Paris)."New value: +"City name (Madrid, Barcelona, London, Paris)"

removedInput schema / properties / limit / description

Removed value: -"Maximum competitors to return (1-50, default 10)."

changedInput schema / properties / sector / description

Previous value: -"ENTIA sector slug (e.g. estetica, dental, psicologia, legal, inmobiliaria, restaurantes, gimnasios, salud)."New value: +"ENTIA sector slug (estetica, dental, psicologia, legal, …)"

AddedMay 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), and the description adds genuinely non-derivable context: paid-plan gating (BUILD or higher, €99/month), Spain-only coverage, and that the response declares alias translation in _meta.sector_resolved_from. Missing only things like rate limits or auth token details.

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-loads the pricing gate and the use case, then layers constraints. Dense but every sentence (paid tier, Spain-only, closed vocabulary, alias resolution) carries operational weight. Slightly packed but not wasteful.

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?

With an output schema present and full parameter documentation in the schema, the description only needs to cover gating, geo scope, and vocabulary behavior — all of which it does. An agent has everything required to decide and call correctly.

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%, so the schema already describes all three parameters including enum values and alias behavior. The description's note that sector is a closed vocabulary and aliases resolve largely restates the schema, adding little beyond it — baseline 3.

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?

States a specific verb+resource+scope: 'Find real competitors in the same sector and city', with ranked entities and Spain-only restriction. This clearly distinguishes it from siblings like entity_lookup, professional_lookup, and get_identity_verification, which are lookups rather than comparative discovery.

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

Usage Guidelines4/5

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

Provides a clear trigger ('Use when the user asks who competes with a business in a sector and Spanish city') plus geo scoping ('Spain only on the public surface'). It does not explicitly name an alternative sibling or state when NOT to use it, keeping it below a 5.

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

All ENTIA Entity Verification tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.