Skip to main content
Glama

jflap_export_table

Export a plain JSON transition table (states, alphabet, start, accepting states, transitions) for a DFA/NFA model, returning a structured error for non-FSA models.

Instructions

Export a plain JSON transition table (states, alphabet, start_state, accepting_states, transitions) for a DFA/NFA model. Returns a structured error for models that cannot be represented as finite state automata.

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": {
      "model": "<model>"
    },
    "name": "jflap_export_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesPath to the .jff automaton file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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; it does disclose the return shape (named JSON keys) and that unrepresentable models produce a structured error rather than crashing. It does not clarify a key ambiguity of the word 'export' — whether the table is returned in the response or written to a file — nor any side effects or overwrite behavior.

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?

Two tight sentences: the payload contents come first, followed by the error condition. No filler, no restatement of the tool name, and every clause conveys usable information.

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?

No output schema exists, so the description usefully lists the returned keys and states the failure mode, which is what an agent needs to consume the result. The one remaining gap is where the exported table lands (in-response vs. on disk), which is left ambiguous for a tool named 'export'.

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% for the single 'model' parameter, so the schema already explains it as a path to the .jff automaton file. The description adds only that the model must be a DFA/NFA, which is marginal meaning beyond the schema; 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?

States a specific verb and resource ('Export a plain JSON transition table') and enumerates the fields it contains (states, alphabet, start_state, accepting_states, transitions) for a DFA/NFA model. The JSON-vs-DOT distinction implicitly separates it from jflap_export_dot, but no sibling is named 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: it exports transition tables for DFAs/NFAs and errors on models that aren't finite state automata, which hints at the applicable input domain. There is no explicit when-to-use statement and no reference to jflap_export_dot or other export/convert siblings as the alternative for a different output format.

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