Skip to main content
Glama

delete_entity_relation

DestructiveIdempotent

Borra la relación entre dos entidades del Atlas. Las entidades no se tocan.

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": {
      "from_entity_id": "<from_entity_id>",
      "to_entity_id": "<to_entity_id>"
    },
    "name": "delete_entity_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_entity_idYesID de la entidad destino (el 'to' de la relación)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
from_entity_idYesID de la entidad origen (el 'from' de la relación)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds meaningful scope information those annotations cannot convey: only the relation is removed and the underlying entities survive, which tells the agent exactly what the destruction touches.

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?

Two short sentences with zero filler; the scope clarification is front-loaded right after the action rather than buried. Nothing is repeated from the name or annotations.

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?

For a simple three-parameter mutation with full schema coverage and rich annotations, the description supplies the one piece of missing behavioral meaning (entities preserved). It says nothing about what happens when the relation does not exist, which is a minor residual gap.

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 from_entity_id, to_entity_id and workspace_id are already fully documented in the schema, including the workspace name/UUID flexibility. The description adds no further parameter guidance, so the baseline 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?

The description names a specific verb ('Borra') and a specific resource ('la relación entre dos entidades del Atlas'), so the operation is unambiguous. It also implicitly separates itself from delete_entity via 'Las entidades no se tocan', though it never names a sibling explicitly.

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?

Usage is only implied: an agent can infer this is the tool for removing an existing relation rather than adding or retyping one. There is no explicit when-to-use statement, no mention of the counterpart tools (add_entity_relation, change_entity_relation_type), and no stated preconditions.

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