Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_blast_radius

Analyze the blast radius of modifying a function or symbol to get a risk zone, PageRank centrality, co-change partners, and confidence details.

Instructions

Analyze the blast-radius (change impact) of modifying a specific function or symbol. Returns a risk zone (SAFE/MEDIUM/HIGH/CRITICAL), PageRank centrality, Git temporal co-change partners, confidence interval, coverage completeness, and residual unknowns.

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": {
      "symbol_name": "<symbol_name>"
    },
    "name": "chronos_blast_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoOutput verbosity: 'summary' (compact 30s glance) or 'complete' (writes full HTML dashboard)summary
file_pathNoFile containing the symbol (helps disambiguate same-name symbols)
symbol_nameYesThe function/class/name_path symbol to analyze (e.g. 'getUser', 'OrderService/create')
max_answer_charsNoOptional maximum character budget for the response (default: 24000; <= 0 disables truncation)
contract_breakingNoSet true if this change modifies the public API signature

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose a rich result profile: risk zone scale, centrality metric, co-change partners, confidence interval, coverage completeness, and residual unknowns. It does not state that the call is read-only or flag that detail='complete' has a filesystem side effect (writing an HTML dashboard), which is only visible in the schema.

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

Conciseness5/5

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

Two tight sentences: the action and scope come first, then a compact inventory of outputs. Every clause carries information and nothing is padded or repeated.

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?

There is no output schema, so the description's enumeration of returned values is necessary and it delivers that adequately for a moderate-complexity analysis tool. The remaining gap is workflow-level: no statement of prerequisites, cost, or how it relates to the mutation and contract siblings.

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 coverage is 100%, so all five parameters, including the enum and defaults, are already documented in structured form. The description adds only that the analyzed entity is a 'specific function or symbol', which the schema's symbol_name example covers anyway, so baseline 3 applies.

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 names a specific verb and resource — analyzing the blast radius of modifying a named function or symbol — and follows it with the concrete artifacts returned (risk zone, PageRank centrality, co-change partners). It is clearly distinguishable from lookup tools, though it never contrasts itself with near neighbors such as chronos_mutation_gate or chronos_contract_status.

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 usage context is implied: the tool is for assessing impact before changing a symbol. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling, so an agent must infer the routing decision on its own.

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