Skip to main content
Glama

jflap_simulate_batch

Batch-simulate many input strings against a .jff automaton in one call and return a verdicts array for each input, enabling language acceptance checks.

Instructions

High-performance batch simulation of hundreds or thousands of input strings on an automaton in a single call. Returns verdicts[] array.

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>",
      "inputs": "<inputs>"
    },
    "name": "jflap_simulate_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesPath to the .jff automaton file
inputsYesList of input strings to simulate
acceptance_modeNoFor PDAs: explicit acceptance criterion ('final_state' or 'empty_stack').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 add real value by disclosing the batching behavior (one call for thousands of strings) and the return shape ('verdicts[] array'), but it says nothing about failure handling for malformed strings, whether one bad input aborts the batch, or any size/performance limits.

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 short sentences, zero waste, and the differentiating detail ('batch', 'single call') is front-loaded ahead of the return-value note.

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 tool with no annotations and no output schema, the definition leaves gaps: the internal structure of verdicts[] is unexplained (does each element carry the input string, an accept/reject flag, a trace?), and PDA acceptance behavior and error handling are unspecified. Adequate to select the tool, thin on how to interpret results.

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 100%, so all three parameters are already documented, including the acceptance_mode enum. The description adds no meaning beyond the schema — notably it never mentions that acceptance_mode matters only for PDAs or what the default is, 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?

States a specific verb and resource: batch simulation of many input strings against an automaton, explicitly 'in a single call'. The word 'batch' and 'hundreds or thousands' implicitly separates it from the single-run sibling jflap_simulate, though that sibling is never named.

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 implied by 'hundreds or thousands of input strings' and 'in a single call', which tells the agent this is the bulk path. It never explicitly says when to prefer jflap_simulate (single string) or jflap_trace (step-by-step), and gives no exclusions or prerequisites.

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