Skip to main content
Glama

tree_verdicts

Retrieves every rule verdict at or under a given path as structured data, including rule details and node status, so viewers can mark and count broken rules without parsing report output.

Instructions

Every rule's verdict at or under path, as data, for a viewer that marks and counts reds: each verdict with the rule, the node ('' for a rule that names no node), the node's name, the verdict (holds, broken, absent, error) and its detail; and each rule that gave one, with its kind, path, description and expression, from the effective tree (pinned packages' rules included). The report tree_check prints, without a parser between it and a page.

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": "tree_verdicts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

B3.4/5.0
Behavior3/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 disclose meaningful scope: the evaluation covers the effective tree including pinned packages' rules, and node is '' when a rule names no node. It never states that this is a read-only operation, says nothing about output size for a broad path or error behavior, so behavioral coverage is partial rather than complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The intent is front-loaded in the opening clause, which is the strongest structural feature. The remainder is one dense semicolon-chained sentence that re-enumerates return fields already covered by the output schema, and the final sentence is a vivid but low-information framing of the same idea.

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?

An output schema exists, so the tool need not explain return values, and the core semantics an agent needs (subtree scope, effective tree with pinned rules, verdict vocabulary) are all present. What remains missing is minor: path format and any notion of result size or performance on a large tree.

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?

The single `path` parameter has 0% schema description coverage, so the description must compensate and only partly does: 'at or under `path`' conveys that the subtree is included, not just the exact node. It never says what form a path takes (filesystem path vs. node path) or that the empty default means the whole tree root.

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 description states a specific resource and scope ('every rule's verdict at or under `path`, as data') and distinguishes the result from the sibling that renders it ('The report tree_check prints, without a parser between it and a page'). An agent can tell this is the structured-data counterpart of tree_check, though the opening is phrased as a content inventory rather than a verb.

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 contrast with tree_check: use this when you want the report as data rather than as printed output. There is no explicit 'use when / don't use when' statement and no mention of when tree_brief or tree_check would be preferable, so the routing signal is present but indirect.

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