Skip to main content
Glama

loo_read

Parse a Looping (.loo) Merise MCD file and return its entities, associations, and links as JSON for further processing.

Instructions

Read a .loo file and return entities, associations, links as JSON.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .loo file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the return value (entities, associations, links as JSON), which is genuinely useful since there is no output schema, but it says nothing about failure behavior for a missing or malformed file, memory/size limits, or whether the read is non-destructive. For a tool with zero annotation coverage that is only partial transparency.

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 sentence, front-loaded with the verb and resource, with every clause carrying information. It is efficient and readable, though the extreme terseness leaves gaps that are penalized in other dimensions rather than here.

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

Completeness4/5

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

This is a simple single-parameter read tool with no output schema, and the description compensates by naming the returned data categories. Only the error/edge-case behavior is missing, which is minor for a straightforward file reader.

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?

There is a single required parameter and schema description coverage is 100%, with the schema already stating 'Path to the .loo file'. The description adds no semantics beyond that, so the baseline 3 for full schema coverage 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?

States a specific verb ('Read') and resource (a .loo file) plus what it yields ('entities, associations, links as JSON'), which naturally sets it apart from the mutating siblings (loo_add_*, loo_remove_*, loo_rename) and the analysis tools (loo_sql, loo_mld). It does not explicitly name or contrast a sibling, which keeps it just below a 5.

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 you call this to inspect an existing .loo file's contents. There is no statement of when to prefer it over loo_sql or loo_apply_spec, and no prerequisites such as the file needing to exist or be a valid .loo file.

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