Skip to main content
Glama

get_entity_relations

Read-onlyIdempotent

Las relaciones de una entidad: las CARGADAS (entrantes y salientes, con nombres) y las POR CONTENIDO — entidades que aparecen junto a ésta mucho más que por azar aunque nadie haya cargado la relación. Para "¿quién trabaja en X?" o "¿con qué se relaciona X?", las por contenido suelen decir más.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesID de la entidad
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, non-destructive, closed-world), so the bar is lower. The description nonetheless adds genuinely non-obvious behavior: it explains that content-based relations exist without anyone having loaded them and are inferred from co-occurrence beyond chance, which is essential for interpreting results. It stops short of describing ordering, limits, or result shape.

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?

Three sentences, front-loaded with what is returned before the usage hint; the parenthetical gloss on CARGADAS and the dash clause on POR CONTENIDO both carry information. Slight redundancy in restating 'relaciones de una entidad', but nothing wasteful.

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 conveying return content, and it does: it tells the agent to expect named incoming/outgoing loaded relations plus a separate inferred set. Only volume, ordering, and pagination behavior are unaddressed, which is minor for a read-only lookup.

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 both parameters (entity_id, workspace_id) are documented in the schema, including the useful note that workspace_id may be a name or omitted when the token is scoped. The description adds nothing about parameters, so the baseline of 3 applies.

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+resource (returns the relations of an entity) and, unusually, splits them into two named categories: CARGADAS (incoming and outgoing, with names) and POR CONTENIDO (statistically inferred co-occurrence). An agent immediately knows what it gets back. It does not explicitly contrast with siblings such as get_workspace_relations, so it stops short of a 5.

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?

Gives concrete trigger questions ('¿quién trabaja en X?', '¿con qué se relaciona X?') and a decision heuristic — content-based relations often reveal more than loaded ones. That is real when-to-use guidance. It does not state when NOT to use it or name an alternative tool for the workspace-wide case, leaving a gap.

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