Skip to main content
Glama

gograph_uncovered

Read-onlyIdempotent

Identify changed non-test Go lines missing from a go test -coverprofile run and return exact uncovered ranges per file; changed files without coverage data are listed separately.

Instructions

Changed lines of non-test Go files that a go test -coverprofile run never executed, as exact line ranges per file (gograph.uncovered.v1). Lines outside coverage blocks are never reported; changed files without profile data are listed separately. WHEN TO USE: After running tests with -coverprofile, to see which lines of your change no test executed. RETURNS: files with uncovered ranges, changed and uncovered line counts.

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": {
      "coverprofile": "<coverprofile>"
    },
    "name": "gograph_uncovered"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute path of your checkout or worktree (alias cwd).
sinceNoGit ref: compare the working tree with this ref
intentionNoRationale; required with an active session.
session_idNoSession from session_create; omit for none.
uncommittedNoCompare the working tree with HEAD, including untracked files
coverprofileYesRepository-relative go test -coverprofile file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.21

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior. The description adds meaningful traits beyond annotations: only lines inside coverage blocks are reported, changed files without profile data are listed separately, and output consists of exact line ranges per file. It does not cover limits or pagination, but adds useful operational context.

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 front-loads what the tool produces, then provides WHEN TO USE and RETURNS sections. It is dense but not wasteful, and the format identifier and coverage-block caveat each earn their place.

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?

There is no output schema, so the description supplies a return summary with files, ranges, and counts, plus important limitations about coverage blocks and missing profile data. This is complete enough for a six-parameter read-only coverage-diff tool, though it could better explain how since and uncommitted interact.

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 parameter meanings are fully supplied by the schema. The description reinforces that coverprofile is a go test -coverprofile file and implies changed-line comparison, but adds little parameter meaning beyond what the schema already provides.

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 resource: changed lines in non-test Go files that a go test -coverprofile run never executed, with exact line ranges per file and a versioned format. It implicitly distinguishes itself from general coverage tools by scoping to changed lines, but it does not explicitly name a sibling alternative.

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 WHEN TO USE section is explicit: after running tests with -coverprofile, to see which lines of a change no test executed. It lacks when-not conditions or a direct named alternative, but the context for use is clear.

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