Skip to main content
Glama

loo_remove_link

Removes a link between a specified entity and association in a .loo file, helping correct Merise MCD relationships when a connection is no longer valid.

Instructions

Remove the link between an entity and an association.

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": {
      "path": "<path>",
      "entity": "<entity>",
      "association": "<association>"
    },
    "name": "loo_remove_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .loo file
entityYes
associationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the mutation itself. It does not say whether removal is reversible, whether the association or entity must already exist, whether the .loo file is rewritten on disk, or what permissions/errors to expect. For a destructive write operation this is a significant gap.

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?

A single front-loaded sentence with no filler; the verb and resource come first. Its brevity is appropriate structurally, though the terseness leaves real gaps addressed in the other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no annotations and no output schema, the definition is under-specified: it omits identifier formats, failure modes, and the effect on the .loo file. It is minimally enough to guess the intent but not enough to call it reliably against similarly named siblings.

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

Parameters2/5

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

Schema coverage is only 33% — only "path" is documented in the schema, while "entity" and "association" have no descriptions. The description restates those two parameter names but adds no meaning: no indication of identifier format, whether qualified names/paths are required, or how to discover valid values.

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?

"Remove the link between an entity and an association" gives a specific verb (remove) and a specific resource (the link joining two named objects), which cleanly separates it from loo_add_link and from the broader loo_remove. It does not explicitly name a sibling as the alternative, 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 Guidelines3/5

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

The word "link" implies usage when an association relationship must be severed, so the context is implied rather than stated. There is no explicit when-to-use, when-not-to-use, or routing to siblings such as loo_add_link (inverse) or loo_remove_attribute (links vs. attribute values).

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