Skip to main content
Glama

impact_surface

Assess the blast radius of a symbol or path before editing by graphing callers, tests, docs, git history, and repo memories with a risk summary.

Instructions

Pre-edit blast radius for a symbol or path: graph callers/callees, tests, docs, git history, GitHub papertrail, and the repo memories crossing it, with a completeness / risk summary. Run this before changing anything non-trivial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
refNo
limitNo
queryNo
symbolNo
includeNoWhat to include — `tests`, `docs`, `git`, `papertrail`, `text_fallback`, `memories`, ALL on by default (impact's value is the bundled evidence). Omit to keep them; pass an explicit list to narrow, e.g. `["git"]` for git history only.
worktreeNoAbsolute path to a linked git worktree you're working in; serves that worktree's branch overlay over the indexed checkout. Omit (or pass an unrelated path) for the indexed checkout.
resolutionNo
full_memoriesNoReturn full memory bodies + every binding + call paths instead of the default compact, scannable per-memory headers (#37). Full detail is also reachable via `memory_for_symbol` / `memory_for_path` / `memory_for_call_path`.
allow_ambiguousNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool runs a multi-faceted analysis and produces a completeness/risk summary. It implies read-only behavior by recommending use before edits, but does not explicitly state safety or any side effects. Adequate but could be more explicit.

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?

The description is two sentences, front-loaded with the core purpose, then listing included elements and a usage recommendation. Every sentence adds value with no wasted words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters and no output schema or annotations, the description is too brief to fully cover usage, parameter interactions, or the format of the completeness/risk summary. More detail is needed for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (30%). The description only references 'symbol or path' as parameters, ignoring the other 8 parameters (id, ref, limit, query, include, worktree, resolution, full_memories, allow_ambiguous). It fails to compensate for the schema's gaps, providing minimal parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool pre-edit blast radius for a symbol or path, listing specific components (callers/callees, tests, docs, etc.) and providing a completeness/risk summary. It distinguishes itself from sibling tools by being a comprehensive pre-change analysis, while siblings are more focused on specific aspects.

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?

The description advises 'Run this before changing anything non-trivial,' which gives a clear context for when to use the tool. It does not explicitly state when not to use it or provide alternatives, but the usage context is well implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cq27-dev/rag-rat'

If you have feedback or need assistance with the MCP directory API, please join our Discord server