Skip to main content
Glama

get_validation_summary

Idempotent

Returns deterministic validation counts and static correction hints for an existing completed operation by rechecking its report against original hashes; incomplete runs yield no summary.

Instructions

Explain an EXISTING local validation operation, retrieving only its original known run if needed. Revalidate the completed report against original hashes; return deterministic counts and static correction hints. Incomplete/held/failed operations have summary:null. May update local result state; never creates or retries a paid run, alters the report, repairs data, or authorizes import.

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": {
      "operationId": "<operationId>"
    },
    "name": "get_validation_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes

Output Schema

NameRequiredDescriptionDefault
runIdYes
stateYes
summaryYes
newPurchaseYes
operationIdYes
sourceReportYes
reportModifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already state openWorldHint=true, idempotentHint=true, and destructiveHint=false; we do not count points repeated from the annotations. The description adds real context: it may update local result state, it returns summary:null for incomplete, held, or failed operations, and it explicitly rules out creating or retrying a paid run, altering the report, repairing data, or authorizing import. This is a strong explanation of side effects and boundaries, but it stops short of covering auth, rate limits, or failure behavior for an unknown operationId.

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?

Four short sentences, with the purpose front-loaded and the negative constraints grouped at the end, which makes the text dense but easy to scan. The phrase 'retrieving only its original known run if needed' is slightly cryptic but still supports the no-retry boundary.

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?

Because an output schema exists, the description need not explain return values in detail, and it still notes the counts, hints, and null-summary case. Given that the tool has one id parameter, the description covers purpose, mutation scope, and exclusions adequately, but it does not say what happens if operationId is unknown or how to handle an operation whose local state was updated.

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?

There is only one parameter, and the schema description coverage is 0%, so the description must compensate, which it only partly does. Saying 'EXISTING local validation operation' implies that operationId identifies a prior operation, but the semantic 'local' and the format pattern it must satisfy are left entirely to the schema, so the description adds little beyond that.

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 verb, resource, and scope: explain an EXISTING local validation operation, revalidating against original hashes to return counts and correction hints. It distinguishes itself from the start_* siblings by stressing that it acts only on an existing operation and does not create or retry a paid run. It does not, however, explicitly differentiate itself from the closely named sibling get_validation.

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?

The capitalized 'EXISTING' and the statement that it never creates or retries a paid run imply that you should use this only for operations that already exist, rather than to start validation. The description never names get_validation or start_validation as alternatives, and it does not say when to prefer one. The usage guidance is therefore only inferred.

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