Skip to main content
Glama

jflap_lsystem_expand

Expands an L-System from a .jff file to a chosen recursion depth, enabling agents to generate derivation levels for formal-language experiments.

Instructions

Expand an L-System (Lindenmayer system) to a given recursion depth/level.

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": {
      "file": "<file>"
    },
    "name": "jflap_lsystem_expand"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the L-System .jff file
levelNoRecursion depth / derivation level (default 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, yet it discloses no behavioral traits: it does not say whether this is a pure read/compute operation or mutates the .jff file, whether expansion is deterministic, or whether errors occur for non-L-System inputs. The only behavioral hint is the implied recursion semantics of "expand".

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 filler and the core operation stated first. It is appropriately sized but so terse that brevity shades into under-specification rather than disciplined conciseness.

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

Completeness2/5

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

There is no output schema, so the description should explain what an expansion yields — the derived string, a new model, or a file written to disk — and it says nothing about the return value. For a tool whose whole purpose is producing derived output, that omission leaves the agent unable to plan the next step.

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%, so both `file` and `level` are already documented in the schema, including the default of 3. The description restates the level parameter's meaning ("recursion depth/level") without adding format, range, or constraint details beyond the schema, so 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 names a specific verb ("Expand") and resource ("an L-System (Lindenmayer system)"), and disambiguates the acronym, so an agent knows exactly what operation is performed. It stops short of distinguishing this tool from any sibling, but no sibling in the list performs L-System derivation, so confusion risk is low.

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 statement of when to use this tool, when not to, or what alternative to pick. Nothing indicates prerequisites (that the .jff file must contain an L-System definition) or what happens if the file is a different model type, leaving the agent to infer usage entirely.

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