Skip to main content
Glama

loo_add_attribute

Adds an attribute to an entity or association in a .loo Merise MCD file so AI assistants can extend or modify model attributes.

Instructions

Add an attribute to 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>",
      "owner": "<owner>",
      "name": "<name>"
    },
    "name": "loo_add_attribute"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and largely drops it. It does not say whether the write is persisted to the .loo file on disk, whether it is reversible, what happens if the named attribute already exists, or whether the owning entity/association must already exist.

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?

It is a single efficient sentence with the core action front-loaded and no filler. However, its brevity is under-specification rather than discipline: the sentence could carry the missing parameter and behavioral context at minimal cost.

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 and no output schema, the definition is far too thin — the agent knows what the tool broadly does but not how to populate required fields like owner and name or what effect the call has. Only the target ('entity or association') is conveyed beyond the name.

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?

Schema description coverage is only 17% — just 'path' is documented — and the description adds nothing for the five remaining parameters (owner, name, type, pk, position). It never explains what 'owner' refers to, what 'type' values are valid, or what 'pk' and 'position' control, leaving critical semantics 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 ('Add') and resource ('attribute') plus the two target types ('entity or association'), which separates it from loo_add_entity, loo_add_association and loo_add_link. It does not distinguish itself from loo_update_attribute or loo_remove_attribute, so an agent must infer the boundary between adding and updating an existing 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 guidance on when to choose this over loo_update_attribute or loo_add_association, and no stated prerequisites such as the .loo file needing to exist or the owner needing to be defined first. The only usage signal is the implicit 'attribute does not yet exist', which is never stated.

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