Skip to main content
Glama

loo_move

Moves an entity or association to new coordinates in a .loo Merise MCD file, repositioning diagram elements by setting their x and y positions.

Instructions

Move an entity (top-left corner) or association (centre).

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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "loo_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameYes
pathYesPath to the .loo file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds one useful detail — the coordinate anchor differs by target type (top-left for entities, centre for associations) — but says nothing about mutating the .loo file, permissions, reversibility, or error behavior.

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 tightly worded sentence with the verb front-loaded and no filler. However, the parenthetical placement is slightly ambiguous about whether the corner/centre applies to the target or to the coordinates.

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 four-parameter mutation tool with no annotations, no output schema, and only 25% schema coverage, the description is too thin. It omits file-write behavior, coordinate-system details, and error conditions that an agent would need to invoke it confidently.

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 only 25%, with just path documented in the schema, so the description must compensate. It partially does by implying that name identifies the entity or association and by explaining that x/y anchor at the top-left for entities versus the centre for associations, but it leaves coordinate units and name-matching rules unspecified.

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 uses a specific verb ("Move") and names the resource precisely: an entity or an association. It distinguishes the two target types but does not mention any sibling tool or explain how it differs from tools like loo_rename or loo_update_attribute.

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 explicit when-to-use guidance beyond the implied purpose of moving an entity or association. It does not state prerequisites such as requiring an existing .loo file, does not say when not to use it, and does not point to alternatives for other geometry changes.

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