Skip to main content
Glama

sumo_qa_record_mutation

Validate a host-collected mutation summary and persist it as the .sumo-qa/mutation.json artifact that the QA report loads.

Instructions

Validate a host-collected mutation summary and persist it as the .sumo-qa/mutation.json artifact the QA report loads (issue #147 follow-up). FILE/FORMAT PLUMBING ONLY — the host skill runs the mutation tool and the LLM reads its output (any format); this tool runs nothing and infers nothing.

Common natural-language phrasings that map to this tool: "record the mutation result", "save the survivors into the QA report", "persist the mutation summary".

mutation is a dict with optional survivors (>= 0), killed (>= 0), freshness (fresh/stale/unknown/absent), detail (e.g. where survivors live), plus source_tool and generated_at provenance. Omit the counts for a not-measured signal. Validation fails BEFORE any write. Mutation evidence is REPORTED, never gated.

write_to defaults to the conventional .sumo-qa/mutation.json under the target repo; a relative path is confined to root.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootYes
mutationYes
write_toNo.sumo-qa/mutation.json
Behavior4/5

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

Annotations are minimal (readOnlyHint=false, etc.), but the description adds significant behavioral detail: validation occurs before write, evidence is reported not gated, and it runs nothing. No contradiction with annotations.

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?

The description is front-loaded with the main action, includes common phrasings, and details parameters concisely. Every sentence adds value, and the structure is logical and efficient.

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?

The description covers the tool's role, parameter details, and validation behavior. It could mention what happens on validation failure or error cases, but for a plumbing tool with good coverage of inputs, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage in the description, it explains the `mutation` parameter's structure (optional fields, counts, provenance) and `write_to` defaults/path confinement. `root` is not explained but is a common path parameter. This compensates well for the lack of formal param descriptions.

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 clearly states the tool validates and persists a mutation summary to a specific artifact (`.sumo-qa/mutation.json`). It provides common phrasings that map to the tool, distinguishing it from siblings that perform other QA tasks.

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

Usage Guidelines4/5

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

The description explicitly states this tool is for 'FILE/FORMAT PLUMBING ONLY' and that the host skill runs the mutation tool, providing clear context. It does not, however, explicitly list when not to use it or name alternative tools among the siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sumithr/sumo-qa'

If you have feedback or need assistance with the MCP directory API, please join our Discord server