Skip to main content
Glama

loo_update_attribute

Rename an attribute in a .loo Merise MCD file or change its data type and primary key status to keep the model accurate.

Instructions

Rename an attribute or change its type / primary key flag.

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_update_attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
pkNo
nameYes
pathYesPath to the .loo file
typeNo
ownerYes
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden. It implies a mutation of an existing attribute, but says nothing about permissions, whether renaming breaks associations/links that reference the attribute, whether a type change rewrites data, reversibility, or failure 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 short sentence, front-loaded with the action and resource, with no filler. It is efficient, though the terseness contributes to the specification gaps noted elsewhere.

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 six-parameter mutation tool with no annotations, no output schema, and near-zero schema description coverage, the definition is far too thin. An agent cannot tell which parameters belong to the rename path versus the retype/pk path, or what happens on success or failure.

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 description coverage is only 17% (only 'path' is documented), so the description must compensate and largely fails. It hints that 'type' and 'pk' exist via 'change its type / primary key flag', but never explains the crucial 'name' vs 'new_name' distinction, nor what 'owner' selects, leaving the two most ambiguous parameters undocumented 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?

States a specific verb-plus-resource: rename or retype an attribute, including the pk flag. The resource 'attribute' implicitly separates it from loo_rename and loo_add_attribute, but the description never names or contrasts those siblings explicitly.

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?

No when-to-use guidance, no prerequisites (e.g. whether the attribute or .loo file must already exist, whether type changes require an empty attribute), and no routing to loo_rename vs loo_add_attribute/loo_remove_attribute. The agent must infer all selection criteria.

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