Skip to main content
Glama
Sign In
falsepass

falsepass

by Super-Eric
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

falsepass_cancel

Stops a running audit job for an environment by terminating its process group, preserving prior results and marking the job cancelled so a new run can begin.

Instructions

Stop the background job of env (an audit, reach, repro or verify-fix, started by this server or an earlier one): its process group gets SIGTERM, and SIGKILL if it is still there 5 s later. Results stored by earlier runs stay; the job is recorded as "cancelled" and a new one can be started.

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": {
      "env": "<env>"
    },
    "name": "falsepass_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYesthe audit's name as falsepass_init returned it: the folder under workdir/audits/
workdirNothe folder whose audits/ holds the audits (default: the current directory).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the SIGTERM-then-SIGKILL escalation with a 5 s grace period, that prior results are preserved, and that the job is recorded as 'cancelled'. The main gaps are permissions/auth requirements and the response or behavior when the named job is not running.

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?

A single dense sentence with the action front-loaded and the destructive escalation and state effects following in priority order. It is efficient, though the parenthetical job-type list and the mix of signal semantics and state notes make it slightly packed.

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 two-parameter job-control tool with no annotations and no output schema, the description covers the important behavior: how the process is terminated, what is preserved, and the resulting job state. It stops short of describing the return value or the no-such-job case, which would complete the picture.

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 both `env` and `workdir` are already documented in the schema next to the description's audience. The description adds only that the job may originate from 'this server or an earlier one', which slightly broadens the meaning of `env` but is not richer parameter guidance.

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 description states a specific verb and resource ('Stop the background job of `env`') and scopes it to jobs started by 'an audit, reach, repro or verify-fix', which ties it to the sibling tools that launch those jobs. An agent can tell this is the termination counterpart to the launch tools without opening a schema.

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 rather than stated: you call this to stop a running job, and 'a new one can be started' hints at the restart flow. It never says when not to call it (e.g. checking status with falsepass_audit_status first, or what happens if the job already finished), and names no alternative tool.

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

Deploy Server

Other Tools