Skip to main content
Glama

loo_add_association

Add a relation (association) with attributes to a .loo Merise MCD file to model links between entities for MLD, MPD, or SQL exports.

Instructions

Add an association (relation).

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameYes
pathYesPath to the .loo file
attributesNoAttributes: "name" strings or {"name", "type" (e.g. INT, VARCHAR(50), DECIMAL(10,2), DATE, TEXT, or any SQL type), "pk" (bool)}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/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 disclosure burden, and it reveals almost nothing. It does not say whether the association is persisted to the .loo file, whether it requires pre-existing entities, whether duplicate associations are rejected, or what happens on failure. The single sentence confirms only that this is a create-style mutation.

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?

The single sentence is short but that brevity reflects under-specification rather than economy; there is no wasted wording because there is almost no wording. It is front-loaded in the trivial sense of having only one clause.

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 five-parameter mutation tool in a domain-specific modeling system (.loo files) with no annotations and no output schema, the definition is far too thin. An agent cannot determine required preconditions, the meaning of three parameters, or the result of a successful call.

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 40%, with path and attributes documented but name, x, and y undocumented in both schema and description. The description adds no meaning at all about these parameters — notably it never explains what name refers to (the association's name? an endpoint?) or what x/y coordinates are for in a relational association.

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

Purpose3/5

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

The description gives a verb and resource ("Add an association (relation)"), with the parenthetical clarifying that association means relation. However, it does nothing to distinguish this from sibling tools such as loo_add_link or loo_add_entity, and the association-vs-link boundary is left entirely ambiguous.

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 mention of prerequisites (e.g., that the entities being related must already exist), and no pointer to any alternative tool. The agent is left to infer placement among sixteen siblings purely from the name.

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