Skip to main content
Glama

Boundary value generator module with pytest tests

submit_boundary_value_generation
Idempotent

Produce a standard-library Python module that produces boundary values for an integer range, plus pytest tests. Choose this when you need the boundary and just-outside values of an inclusive integer range, with tests. Do not choose this for non-integer ranges, random data generation, or property-based testing frameworks. Example requests: Write a Python module that produces the boundary and just-outside values for an integer range, with tests. | I need boundary values for an inclusive integer range for test data. | Generate a boundary-value module 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_boundary_value_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.1/5.0
Behavior3/5

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

Annotations already declare write (readOnlyHint=false), idempotent, non-destructive and non-open-world, and the schema documents quote_id/authorization. The description adds the deliverable shape (module + pytest tests) and template-fixed behaviour. It is silent on the fact that this submits a priced job whose price must match a quote, and on whether the result is returned inline or as a job — the most consequential behavioural traits for a submit_* tool.

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?

Front-loaded with the deliverable, then exclusions, then examples — a sensible order. The three example requests largely restate the first sentence and pad length slightly, but each is short and reads as disambiguation rather than filler.

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?

Output schema exists, so return values need no explanation, and the schema covers parameters and pricing. The description supplies scope, exclusions and examples. The only meaningful gap is the job/pricing lifecycle and result-retrieval behaviour, which the description never mentions and which an agent must discover elsewhere.

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% and the nested template/module_name/function_name fields are all documented in-schema, so baseline 3 applies. The description adds only that the range is integer and inclusive; it says nothing extra about module_name/function_name conventions, the fixed 'boundary-values' template, or how quote_id/accepted_price interact.

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?

States a specific verb and deliverable: 'Produce a standard-library Python module that produces boundary values for an integer range, plus pytest tests.' It immediately scopes the tool to integer ranges and pytest-verified output, which separates it from the many other submit_* generator siblings without the agent needing to open a sibling schema.

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?

Explicitly says when to choose it ('when you need the boundary and just-outside values of an inclusive integer range, with tests') and when not to ('non-integer ranges, random data generation, or property-based testing frameworks'). Three example requests reinforce the intended phrasing, leaving nothing to inference.

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