Skip to main content
Glama
shivyadavus

Open Kioku

by shivyadavus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Open Kioku Explain Test Coverage

explain_test_coverage
Read-onlyIdempotent

Retrieve indexed test-coverage evidence for any file or the entire repository, including coverage percentages and associated test suites. Use it to inspect previously stored coverage data without running tests.

Instructions

Retrieve stored test-coverage evidence and associated test suites for one repository-relative file or the whole repository. Returns coverage percentages, test file associations, and suite metadata from indexed data. Use to inspect stored test-coverage evidence for one file path or the whole repository. Returns associated test suites, coverage percentage when available, and test file associations from indexed metadata. Do NOT use to decide what tests to run next (use recommend_validation_plan) or to find tests for a specific change (use find_tests_for_change). This is read-only, does not execute any tests, and reports only previously indexed or stored coverage data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoRepository-relative path of the file to inspect coverage for. If omitted, returns repository-wide coverage summary.
limitNoMaximum number of coverage entries to return. Defaults to 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoWrapped non-object output, used for Markdown, TOON, or scalar responses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.3
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum coverage elements to return. Defaults to 20."New value: +"Maximum number of coverage entries to return. Defaults to 20."
    • changedInput schema / properties / path / description
      Previous value: -"The repository-relative path of the file."New value: +"Repository-relative path of the file to inspect coverage for. If omitted, returns repository-wide coverage summary."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The MCP structuredContent object returned by this Open Kioku tool. Most tools expose their JSON fields directly; string or scalar tool outputs are wrapped as {\"value\": ...}.",
+  "properties": {
+    "value": {
+      "description": "Wrapped non-object output, used for Markdown, TOON, or scalar responses."
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changedv2.0.3
    • addedInput schema / properties / limit / description
      Added value: +"Maximum coverage elements to return. Defaults to 20."
    • addedInput schema / properties / path / description
      Added value: +"The repository-relative path of the file."
  3. First observedv2.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Description discloses that the tool is read-only, does not execute tests, and reports only indexed data. This adds context beyond annotations (readOnlyHint=true, destructiveHint=false) by specifying behavioral traits like 'does not execute any tests'.

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?

Description is relatively concise and front-loaded, though repetitive in parts (first and third sentence overlap). Efficient overall.

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?

Given presence of output schema, annotations, and sibling tools, the description covers purpose, usage, limitations, and return value types (coverage percentages, test file associations, suite metadata). Complete.

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%; description does not add significant meaning beyond schema for parameters. Baseline 3 is appropriate.

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?

Description uses specific verb 'Retrieve stored test-coverage evidence' and clearly identifies the resource: one file or whole repository. It distinguishes from siblings like recommend_validation_plan and find_tests_for_change.

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 use the tool (inspect stored coverage) and when not to, providing alternative tools (recommend_validation_plan, find_tests_for_change).

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