Skip to main content
Glama

loo_mpd

Converts a Looping .loo Merise model into a physical data model (MPD) in Markdown and optionally writes it to a specified .md file.

Instructions

Return the physical model (MPD) as Markdown; also write it to out when given.

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

Input Schema

NameRequiredDescriptionDefault
outNoOptional output .md path
pathYesPath to the .loo file
dialectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it usefully discloses the dual behavior of returning Markdown and additionally writing a file to `out`. It says nothing about whether an existing `out` file is overwritten, whether the file must exist, permission requirements, or what happens on an invalid model.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single clause-pair sentence that front-loads the primary return value and appends the optional side effect. No filler, no redundancy.

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 simple three-parameter read tool with no output schema, the description covers the core behavior adequately. It falls short on the dialect parameter's effect and on write-side details for `out`, which matter because the tool has an unannotated filesystem side effect.

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?

The clause 'also write it to `out` when given' only restates the schema's own 'Optional output .md path'. The `dialect` enum parameter, which controls generated DDL flavor, is undocumented in both the schema and the description, leaving a real semantic gap.

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 names a specific verb and resource ('Return the physical model (MPD)') and states the serialization format (Markdown), so the agent knows exactly what comes back. It does not differentiate from the sibling loo_mld, which is the obvious near-neighbor an agent could confuse it with.

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 explicit when-to-use framing and no mention of alternatives, prerequisites, or exclusions. An agent must infer from the name that this is the read/inspect step after a model has been built, and there is no hint about choosing this over loo_mld or loo_sql.

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