Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_mutation_gate

Run targeted mutation testing on a source file, generate mutants, select covering tests, execute them in parallel sandboxes, and return a mutation score to enforce dev or release quality gates.

Instructions

Run targeted mutation testing on a specific file using CHRONOS's Mutation Arena. Generates mutants, selects covering tests via 4D graph, runs them in parallel sandboxes, and returns the mutation score.

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": {
      "file_path": "<file_path>"
    },
    "name": "chronos_mutation_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
strictNoUse 90% threshold (release gate). Default false = 80% dev gate.
file_pathYesPath to the source file to mutation-test
test_commandNoTest runner command (default: 'npx jest --passWithNoTests')npx jest --passWithNoTests
max_answer_charsNoOptional maximum character budget for the response (default: 24000; <= 0 disables truncation)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 internal pipeline: mutant generation, 4D-graph test selection, parallel sandboxes, score return. Missing are the traits an agent needs to plan around a heavy operation: expected duration/cost, whether sandboxes or mutants leave artifacts, prerequisites (test tooling in the repo), and failure behavior when the test command fails.

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?

One front-loaded sentence with no filler; the purpose comes first and the pipeline detail follows. Slightly dense, but every clause conveys something about what the tool does.

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?

The one required parameter is well documented and the return value is named, which is reasonable for a parameterless-output tool. However, with no annotations and no output schema, the definition should say more about the shape of the result (score only, or per-mutant detail) and the operational cost of a mutation run.

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 100%, so all four parameters are already documented, including the 90% vs 80% gate semantics for 'strict' and the default test command. The description adds no parameter meaning beyond what the schema states, so the baseline of 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 (run mutation testing on a specific file) plus the mechanism (Mutation Arena) and the output (mutation score). That is clearly distinguishable from the graph/query/symbol-edit siblings, though it does not name an alternative explicitly.

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 only implied: an agent can infer it should call this when it wants a mutation score for one file, and the 'strict' parameter hints at release-gate usage. There is no explicit statement of when to prefer this over running tests directly, or when not to use it (e.g., whole-repo runs, files without coverage).

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