Skip to main content
Glama

loo_remove

Delete an entity or association from a .loo file, including its links, to remove unwanted model elements.

Instructions

Delete an entity or association and its links.

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>",
      "name": "<name>"
    },
    "name": "loo_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathYesPath to the .loo file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/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 only one trait: deletion is cascading, since the entity or association goes away together with its links. It says nothing about irreversibility, whether the .loo file is rewritten in place, or what happens if the name is not found.

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 tight sentence with the operation and the cascade effect front-loaded, and no wasted wording. It is perhaps too terse for a destructive operation, but the structure itself is clean.

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

Completeness2/5

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

For a destructive, two-required-parameter tool with no annotations and no output schema, the definition omits the things an agent needs before invoking it: confirmation of irreversibility, the semantics of the name argument, and the outcome of a failed deletion.

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 50%: path is documented in the schema, but name has no description. The description hints that name may refer to either an entity or an association, yet it never states the expected format (qualified name, namespace, case sensitivity) for either case.

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 concrete verb ("Delete") plus the resource ("an entity or association and its links"), so the agent knows this removes model elements rather than attributes or links alone. It does not distinguish itself from loo_remove_attribute or loo_remove_link, but the object of deletion is explicit enough to route correctly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g., whether the entity must already exist in the .loo file), and no mention of the sibling tools for narrower removals. The agent must infer usage purely from the verb.

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