Skip to main content
Glama

Regression suite generator with pytest tests

submit_regression_suite_generation
Idempotent

Produce a standard-library Python module that turns recorded input/output pairs into a pytest module, plus pytest tests. Choose this when recorded input/output pairs must become one deterministic pytest case per pair. Do not choose this to test behaviour not covered by the recorded pairs, or to generate non-deterministic tests. Example requests: Write a Python module that turns recorded input/output pairs into a pytest module, with tests. | I have input/output examples and want a deterministic regression test suite. | Generate a regression-suite generator and prove it with pytest.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_regression_suite_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds material context beyond that: the output is standard-library Python, one deterministic case per recorded pair, and behaviour is fixed by the selected template. It does not mention the priced-job/quote flow, but the schema covers that in quote_id.

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?

It is front-loaded with the purpose, then the when/when-not conditions. The three example requests are useful for matching user phrasing but are somewhat repetitive and could be trimmed without losing 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?

For a tool with a nested input object, four parameters, an output schema, and rich annotations, the description covers purpose, scope, exclusions, and output form. It leaves pricing/authorization mechanics to the schema, which is reasonable given the quote_id description, but a brief note about the job-submission nature would fully close the gap.

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 75%, so the nested inputs, quote_id, authorized_by, and accepted_price are already documented. The description adds no parameter-specific meaning beyond the example phrases, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and artifact: a standard-library Python module plus pytest tests that maps recorded input/output pairs into a pytest module. This distinguishes it from siblings like submit_boundary_value_generation or submit_python_utility_module without requiring the schema to be opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit positive trigger ('when recorded input/output pairs must become one deterministic pytest case per pair') and explicit exclusions ('Do not choose this to test behaviour not covered by the recorded pairs, or to generate non-deterministic tests'). The example requests reinforce the routing decision.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources