Skip to main content
Glama

loo_sql

Generates a SQL DDL script from a .loo Merise model and optionally writes it to a specified output .sql file.

Instructions

Return the SQL DDL script; 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_sql"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the key side effect (writing a .sql file when `out` is supplied), but not whether an existing file is overwritten, whether the returned text equals the written file, or what happens on an invalid model. For a tool that touches the filesystem, that leaves notable gaps.

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 front-loaded sentence with no wasted words; the return behavior leads and the optional write is subordinated. It is efficient but arguably too terse given the tool's three parameters.

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?

No output schema and no annotations, so the description should say more about the returned value (plain SQL string? file path? both?) and about dialect selection. It covers the core and the `out` side effect but stops short of what an agent needs for full confidence.

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 `out` are documented in the schema, and the description usefully clarifies that `out` triggers a write in addition to returning the script. However, the `dialect` enum — the parameter most likely to change output — is never mentioned in either the description or the schema.

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?

States a specific verb and resource: 'Return the SQL DDL script' from a .loo file, plus the optional write side effect. That distinguishes it from model-editing siblings like loo_mld or loo_add_entity, though it never names or contrasts 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 converts a .loo model into SQL DDL. There is no statement of when to prefer it over sibling tools, no prerequisites (e.g., must the model be validated first), and no exclusions.

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