Skip to main content
Glama

loo_apply_spec

Adds every object from a spec to an existing .loo file, enabling bulk extension of Merise MCD models.

Instructions

Add every object of a spec (same shape as new) to an existing file.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .loo file
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a bulk addition to an existing file, but says nothing about duplicate handling, conflict behavior, atomicity, required permissions, or what the operation returns.

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?

The definition is a single front-loaded sentence with no wasted wording. Its only weakness is the cryptic reference to `new`, which relies on sibling context to be fully understood.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with a nested `spec` object and no annotations or output schema, the description is quite thin. It establishes the core action and bulk behavior but leaves important operational details undocumented.

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?

The schema documents `path` and leaves `spec` as an undescribed object, giving 50% coverage. The description partially compensates by explaining that `spec` contains every object to add and has the same shape as `new`, but it does not specify the object structure or required fields.

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: adding every object of a spec to an existing file. It implicitly distinguishes this bulk-spec operation from creating a new file via the referenced `new` shape, though it does not name sibling alternatives explicitly.

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?

It implies usage for applying a complete spec to an existing file, but gives no explicit when-to-use guidance, no exclusions, and no comparison to the add/update/remove sibling tools. The agent must infer the appropriate context.

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