Skip to main content
Glama

loo_mld

Extract the logical model (MLD) as text from a specified .loo file to support Merise database design and SQL export workflows.

Instructions

Return the logical model (MLD) as text.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .loo file

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 supplied, so the description carries the whole burden, and all it reveals is that the return value is text. It does not say whether the call is read-only (implied by 'Return' but not stated), whether the output may be large, or what happens when the path is invalid or the model is empty.

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?

One short sentence with the key information, the output type, front-loaded after the verb. It is efficient, though the '(MLD)' gloss adds little for an agent already reading the tool name.

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 single-parameter, schema-documented read tool with no output schema, the description is adequate to call the tool correctly. It leaves open the practical questions that matter for this family of tools: which file state it reflects and how it differs from the physical-model sibling.

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 description coverage is 100%: the single path parameter is documented as the path to the .loo file. The description adds nothing beyond that and does not need to, so the baseline 3 applies.

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 gives a specific verb and resource: return the logical model (MLD) as text, and it expands the acronym, which helps. It does not distinguish the tool from the closest sibling that could return another model representation, loo_mpd, so an agent must infer the split between logical and physical model.

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 statement of prerequisites such as whether the file must first be loaded or a spec applied, and no routing away from loo_mpd or loo_sql. An agent must guess that this is the logical-model counterpart of the physical-model tool.

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