Skip to main content
Glama

get_atf_code_coverage

Read-only

Returns ATF code coverage for business rules, script includes, and other scripts, with covered/executable lines, coverage percentages, related tests, and recently changed untested scripts.

Instructions

ATF code coverage (sys_atf_code_coverage, Australia and later): covered and executable lines per business rule, script include and other script, merged across test runs, with coverage percent and the tests that hit each script. Also lists scripts changed recently that no test covers, and ATF test, suite and Test Generator totals. Read-only

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_atf_code_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax scripts per list (default 30)
changed_daysNoWindow for "recently changed and untested" scripts (default 90)
script_tableNoOnly one script table, e.g. sys_script or sys_script_include

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered and the trailing 'Read-only' adds nothing. Beyond that, the description does add real behavioral context: results are merged across test runs, the version applicability is 'Australia and later', coverage is expressed as both line counts and a percentage, and per-script test attribution is included. It omits cost/latency or size characteristics, but the aggregation and version semantics are substantive.

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?

The definition is a single dense, front-loaded sentence that opens with the resource and table name, followed by a minimal 'Read-only' tag. It is a long sentence but every clause carries information about scope or output; the only wasted element is the redundant 'Read-only' that repeats the annotations.

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?

With only three optional parameters, no output schema, and no nested objects, the description carries the burden of explaining return values — and it does so in detail (line counts, coverage percent, hitting tests, untested-recently-changed list, test/suite/generator totals). Version applicability is also stated. Missing only minor operational details like result ordering or pagination behavior.

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 the baseline is 3. The description corroborates the intent of the parameters — 'recently changed and untested scripts' maps to changed_days, and 'per business rule, script include and other script' clarifies what script_table scopes — but it adds no syntax, format, or default details beyond what the schema already states (default 30, default 90, example table name).

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 names a specific resource (sys_atf_code_coverage, ATF code coverage, Australia and later) and enumerates exactly what it returns: covered/executable lines per business rule, script include and other script, merged across test runs, plus coverage percent, per-script test attribution, recently changed untested scripts, and ATF test/suite/Test Generator totals. This is clearly distinct from sibling tools such as get_atf_suite_result or list_atf_test_results, which deal with test outcomes rather than script coverage.

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 implied by the content clauses — you would call this to measure script coverage or to find recently changed scripts no test covers — but there is no explicit when-to-use/when-not statement and no alternative tool is named for related questions. An agent can infer the right context, but must reason about it rather than being told.

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