Skip to main content
Glama

Correlate Static And Runtime

correlate_static_and_runtime
Idempotent

Tests caller-declared hypotheses connecting static comparison findings to runtime comparison dimensions, returning all correlations with complete Evidence closure inline.

Instructions

Evaluate every explicit caller-declared hypothesis between exact static comparison findings and runtime comparison dimensions. Similar names or paths are never auto-matched, consistent cochange never proves causality, and unknown or truncated inputs remain unresolved. Returns all correlations and their complete Evidence closure inline.

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": {
      "static_comparisons": "<static_comparisons>",
      "runtime_comparisons": "<runtime_comparisons>",
      "mappings": "<mappings>"
    },
    "name": "correlate_static_and_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
mappingsYes
static_comparisonsYes
runtime_comparisonsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety bar is lower. The description still adds genuine operational context: no fuzzy auto-matching, cochange does not establish causality, unknown or truncated inputs remain unresolved, and the full Evidence closure is returned inline rather than paginated.

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?

Three dense sentences, front-loaded with the verb and resource, with each clause adding a distinct rule (no auto-match, no causality, unresolved unknowns, full closure returned). Some phrasing is jargon-heavy but nothing is redundant.

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?

Given a deeply nested Evidence input schema and no output schema, the description usefully states what comes back (all correlations plus complete Evidence closure inline). It does not, however, explain the top-level input shape or the selector/hypothesis nesting an agent must construct, leaving a real gap for a tool this complex.

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?

Top-level schema description coverage is reported at 0%, so the description carries weight. It implicitly maps its three inputs (static comparison findings, runtime comparison dimensions, declared hypotheses) and stresses that identifiers must be exact, but it never mentions the mappings' side_alignment or expected_pattern semantics that determine whether input is rejected.

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?

Names a specific verb+resource: it correlates caller-declared hypotheses between static comparison findings and runtime comparison dimensions. That distinguishes it from nearby compare_* tools, though it never names an alternative explicitly and leans on domain jargon ("Evidence closure") the agent must already know.

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 line "every explicit caller-declared hypothesis" and "never auto-matched" implicitly tells the caller they must supply mappings rather than rely on name/path matching, which is real usage context. However, there is no explicit when-to-use vs when-not guidance and no pointer to sibling comparison tools.

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