Skip to main content
Glama

loo_add_entity

Add a new entity with attributes to a Looping .loo Merise MCD file, defining names, SQL types, and primary keys for your data model.

Instructions

Add an entity.

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

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

D1.3/5.0
Behavior1/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, yet it says nothing about persistence to the .loo file at path, whether the file must already exist, whether the entity is written immediately, or whether the operation can fail or be undone. For a mutation tool with zero annotation coverage this is a complete gap.

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?

It is short to the point of under-specification rather than concise; there is no wasted wording but also no front-loaded information about the resource, the file target, or the resulting entity.

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?

With five parameters, two required, a file-path target, a polymorphic attributes array, no annotations and no output schema, the definition supplies none of the context needed to call it correctly or predict its effect.

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 40%: the x and y coordinates and the name parameter are entirely undocumented, and the description contributes no parameter meaning at all. It does not explain the coordinate semantics, whether name must be unique, or how attributes interact with later loo_add_attribute calls.

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

Purpose2/5

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

"Add an entity" restates the tool name loo_add_entity with a verb and a noun but does not say what an entity is in a .loo model, what adding one accomplishes, or how it differs from siblings like loo_add_attribute or loo_add_association. An agent cannot distinguish its scope from adjacent add-operations without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, no mention of alternatives such as loo_add_attribute for column-like data or loo_add_association for relationships. The single sentence leaves the agent to infer everything.

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