Skip to main content
Glama

loo_set_card

Change the cardinality of an existing link in a Looping (.loo) Merise MCD file. Provide the file path, entity, association, and new cardinality to update link constraints.

Instructions

Change the cardinality of an existing link.

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>",
      "entity": "<entity>",
      "association": "<association>",
      "card": "<card>"
    },
    "name": "loo_set_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYes
pathYesPath to the .loo file
entityYes
associationYes

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?

With no annotations, the description carries the full behavioral burden and provides almost nothing: not whether the change is in-place or destructive to existing data, not whether the .loo file must be otherwise valid, and not what happens if the new cardinality conflicts with existing associations. Only 'existing link' hints that the target must already be present.

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?

A single front-loaded sentence with zero filler, which is structurally clean. However, its brevity is under-specification rather than economy, given a four-required-parameter mutation.

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 mutation tool with four required parameters, no annotations, no output schema, and a schema that documents one field, this description leaves far too much for the caller to guess. The most consequential unknown, the cardinality value syntax, is entirely absent.

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 25% (just `path` is documented), so the description needed to compensate and does not. It never explains the accepted `card` format (e.g. "1..*", "0..1"), what `entity` and `association` identify, or how they jointly locate the link to modify.

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 and resource ("Change the cardinality of an existing link"), which is enough to distinguish it from siblings like loo_add_link or loo_remove_link. It does not explicitly name those siblings, but the operation is unambiguous at a high level.

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 use this versus loo_add_link (which presumably sets cardinality at creation) or loo_add_association. No prerequisites, no note about the link needing to already exist beyond the word 'existing', and no exclusions are given.

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