Skip to main content
Glama

loo_new

Creates a new .loo Merise MCD file and optionally fills it from a model spec containing entities, associations, attributes, and links.

Instructions

Create a new .loo file, optionally filled from a spec {entities:[{name, attributes, x?, y?}], associations:[...], links:[{entity, association, card}]}.

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": "loo_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .loo file
specNoOptional model spec
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it does not say what happens if the target file already exists, what the default for overwrite is, whether existing content is lost, or what the call returns. For a filesystem-mutating creation tool with zero annotation coverage, that is a substantial gap.

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 sentence, verb-first, with no filler. The inline spec sketch is dense but informative rather than redundant; it could be easier to scan if the overwrite behavior were also stated, but nothing is wasted.

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?

With no annotations and no output schema, the definition should describe the creation semantics and the overwrite condition; it does neither. An agent knows how to build the spec but not how the tool behaves on an existing path, which is the main failure mode for this operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%: path and spec have descriptions, overwrite has none. The description does add real meaning for spec by sketching the entity/association/link shape (including optional x/y and the link's entity/association/card triple), but it says nothing to compensate for the undocumented overwrite flag.

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: "Create a new .loo file", plus a scope qualifier ("optionally filled from a spec"). That distinguishes it from read/modify siblings like loo_read or loo_apply_spec, though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the entry point for a brand-new model versus loo_apply_spec on an existing one, but the description never states when to use this versus that sibling, nor any prerequisites. No exclusions or when-not guidance are given.

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