Skip to main content
Glama

loo_remove_attribute

Remove a specific attribute from a Looping (.loo) Merise MCD file by specifying the file path, owner, and attribute name.

Instructions

Remove an attribute.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
pathYesPath to the .loo file
ownerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.6/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 delivers none of it. It does not say whether removal is reversible, what happens to references or associations pointing at the attribute, or what permissions the owner argument implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but only because it is under-specified rather than efficient. There is no front-loaded scope, no constraints, and nothing that earns its place beyond the name.

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

Completeness1/5

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

For a three-parameter mutation with no annotations and no output schema, the definition is drastically incomplete. An agent cannot determine preconditions, side effects, or return behavior from this text.

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

Parameters1/5

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

Three required parameters with only 33% schema description coverage (only path is documented), and the description adds no meaning for name, owner, or path. The single sentence does not compensate for the coverage gap at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Remove an attribute" is a verbatim restatement of the tool name loo_remove_attribute, adding no scope or distinction. It gives no clue how it differs from loo_remove, loo_update_attribute, or loo_remove_link.

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

Usage Guidelines1/5

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

The description contains no when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent has nothing to route on besides the name.

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