Skip to main content
Glama

henry_explain_finding

Explains a previously reported finding by ID so you can see the evidence and reasoning behind why an observation or inference was flagged during compatibility analysis.

Instructions

Explain a previously produced finding by its ID.

Use after henry_inspect_file, henry_analyze_pair, or henry_predict_failure_scenarios to understand why a particular observation or inference was reported.

Args: finding_id: The ID of the finding to explain.

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": {
      "finding_id": "<finding_id>"
    },
    "name": "henry_explain_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
finding_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden; it does disclose the important state dependency that the finding must have been produced earlier. It says nothing about whether the call is read-only, what happens if the ID is unknown or stale, or how far back findings persist.

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?

Front-loaded with the purpose in the first sentence, then the usage guidance, then the argument note; nothing is padded. The line-wrapped phrasing is slightly awkward but costs no clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value explanation is not needed, and the provenance guidance covers the main flow. Gaps remain around failure behavior for invalid or expired IDs and the read-only nature of the operation, which matter for an ID-keyed lookup.

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% for the single finding_id parameter, so the description must compensate; "The ID of the finding to explain" mostly restates the field name. The qualifier "previously produced" does add the useful hint that the ID originates from a prior tool's output.

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?

"Explain a previously produced finding by its ID" pairs a specific verb with a specific resource and makes clear this is a follow-up to analysis rather than an analysis itself. It contrasts implicitly with the sibling tools that generate findings, so an agent can tell the two roles apart without reading schemas.

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?

It explicitly names the three tools whose output precedes this call (henry_inspect_file, henry_analyze_pair, henry_predict_failure_scenarios), which is strong sequencing guidance. It stops short of stating when not to use it or what to do if no prior finding exists.

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