Skip to main content
Glama

loo_rename

Rename an entity or association in a Looping .loo file by specifying the file path and old/new names to update the MCD model.

Instructions

Rename an entity or 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>",
      "old": "<old>",
      "new": "<new>"
    },
    "name": "loo_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
newYes
oldYes
pathYesPath to the .loo file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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, yet it only says the operation renames. It does not disclose failure modes (unknown name), whether references to the renamed symbol are updated, whether the change is persisted atomically, or whether prior state is recoverable.

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

Conciseness3/5

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

The single sentence is tight and front-loaded with the verb, with no filler. However, brevity here reflects under-specification rather than effective economy given a three-parameter mutation tool.

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 required-parameter rename operation with no annotations and no output schema, the definition leaves too much unsaid: no error behavior, no confirmation of what a successful call returns, and no explanation of the file-path parameter's role beyond the schema string.

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% (just 'path' is documented). The description adds no meaning for 'old' and 'new' — it does not say whether 'old' is an existing name or a pattern, or whether 'new' must be unique — so the undocumented parameters remain unexplained in both places.

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 states a specific verb ('Rename') and a specific resource class ('entity or association'), so an agent can tell it apart from add/remove/update siblings. It stops short of naming the file context that the 'loo_' family implies.

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 statement of prerequisites, and no indication of what happens when 'old' does not exist or when the name is already taken. Nothing routes the agent to or away from this tool versus loo_update_attribute or loo_move.

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