Skip to main content
Glama

clear_manual_coverage

Reset the accumulated manual-recording dimension for a branch.

Manual uploads are additive: each upload_local_coverage with coverage_kind="manual" unions that hand-driven session into the branch's manual dimension, so you can build a pass up one flow at a time. Call this to wipe that accumulation and start over — every function goes back to Unexercised. The branch's manual_languages are kept, so the Manual Recording view stays visible; only the per-function coverage is cleared.

This does not touch browser coverage (coverage_kind="browser"), which has no clear at all: every producer there replaces its own contribution on its next run, so nothing accumulates to be reset.

repository is the GitHub 'owner/repo' (a repo UUID also works); branch defaults to the repository's default branch. Errors when the branch has no local analysis to clear. Returns cleared_functions — the number of function rows reset.

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": {
      "repository": "<repository>"
    },
    "name": "clear_manual_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNo
repositoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/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 so: it discloses what is destroyed (per-function coverage to Unexercised), what survives (manual_languages, so the Manual Recording view stays visible), a failure mode (no local analysis), and the return value (cleared_functions count).

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 action in the first line, then layered detail in short paragraphs. It is somewhat long, and the browser-coverage aside is more context than strictly needed to call the tool, but every paragraph remains scannable and on-topic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a two-parameter mutation with no output schema: preconditions, scope of destruction, preserved state, error condition, and return field are all covered, leaving nothing an agent needs before invoking it.

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

Parameters5/5

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

Schema coverage is 0%, and the description compensates fully: repository is 'owner/repo' (UUID also accepted) and branch defaults to the repository's default branch. Neither fact is derivable from the bare string/null schema.

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?

Opens with a specific verb and resource: 'Reset the accumulated manual-recording dimension for a branch.' It immediately distinguishes this from the closest sibling by naming upload_local_coverage and coverage_kind="manual" as the thing being undone.

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 states when to call it ('Call this to wipe that accumulation and start over'), gives the precondition ('Errors when the branch has no local analysis to clear'), and excludes the adjacent case by explaining browser coverage has no clear at all. No inference required.

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