Skip to main content
Glama

list_untested_functions

List functions in an analysis, filtered by coverage state.

state_filter is a comma-separated subset of untested,partial,covered. Default skips fully-covered functions — those are typically what an agent looking for "tests to write" cares about.

Rows include React sub-units — an inline JSX handler (Component.<onSubmit>, kind="handler") or a conditional render branch (Component.<branch#1>, kind="render_branch") — because "this component's error state never rendered" is usually the actionable gap, not "this component is 80% covered". Filter on kind in ("function", "component") when you want whole functions only.

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": {
      "analysis_id": "<analysis_id>"
    },
    "name": "list_untested_functions"
  }
}

Input Schema

NameRequiredDescriptionDefault
analysis_idYes
state_filterNountested,partial

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose real behavior: the default filter excludes fully-covered functions, and rows may include synthetic React sub-units with specific id conventions (Component.<onSubmit>, Component.<branch#1>) and kind values. Missing are any notes on result volume, pagination, or read-only/mutation semantics.

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?

Purpose and the default-behavior rationale are front-loaded, and the sub-unit explanation is concrete rather than padded. The final sentence about kind filtering is the weak link — it spends words on a capability the schema does not expose.

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?

An output schema exists, so return-field documentation is not required, and the description stays within its lane while still explaining the non-obvious shape of returned rows. Combined with explicit default-filter semantics for an unannotated tool, an agent has enough to call it correctly.

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 0%, so the description must compensate, and it does well for state_filter by enumerating untested/partial/covered and explaining the default. However, analysis_id is never described, and the closing instruction to 'Filter on kind in ("function", "component")' references a parameter that does not exist in the input schema, which could lead an agent to pass an invalid argument.

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?

The first sentence gives a specific verb and resource ('List functions in an analysis') plus the scoping dimension ('filtered by coverage state'), which separates it from list_analyses (analyses, not functions) and get_function_detail (single function detail). It stops short of naming that detail sibling explicitly, so the agent must infer the boundary.

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 supplies a clear usage context: the default skipping of fully-covered functions is justified by 'those are typically what an agent looking for "tests to write" cares about'. It also tells the agent when to narrow to whole functions only. It never states when not to use this tool or names the alternative for single-function inspection.

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