Skip to main content
Glama

Run Python test

proof_run_python_test

Runs a single workspace-relative Python test file to execute local code and return runtime evidence for validation, not formal proof.

Instructions

Run one workspace-relative Python test file. This executes local code and is runtime evidence, not a formal proof.

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": {
      "filePath": "<filePath>"
    },
    "name": "proof_run_python_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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, and it does disclose the key risk that this executes local code and produces runtime evidence rather than a formal proof. It omits sandboxing, timeout behavior, permission requirements, and whether execution can mutate workspace state — meaningful gaps for a code-execution tool.

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 with zero padding. The action and its scope come first, and the important caveat about it being runtime evidence is front-loaded rather than buried.

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 one-parameter execution tool with no annotations and no output schema, the description covers what it does and the nature of the evidence, but says nothing about what the agent receives back (pass/fail, stdout, exit code) or execution limits. An agent can call it, but cannot predict or interpret the result from the definition alone.

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 0% for the single filePath parameter, so the description must compensate. It adds that the path is workspace-relative and refers to exactly one test file, which is genuinely useful, but it doesn't clarify extension expectations, whether directories are rejected, or how the path is resolved.

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: run one workspace-relative Python test file. The clause 'runtime evidence, not a formal proof' implicitly separates it from the proof_check_* siblings, though no sibling is named directly.

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 the 'runtime evidence, not a formal proof' framing, which tells the agent this is for empirical test execution rather than static verification. However, it never explicitly says when to pick this over proof_run_approved_checks or proof_discover_qa, leaving routing to inference.

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