Skip to main content
Glama
Sign In
mcp-injector

mcp-injector

by foldwork-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

injector_blast_radius

Identify dependencies of a symbol to understand refactor blast radius. Traverse inbound, outbound, or both directions.

Instructions

Finds dependencies of a specific symbol to analyze the impact of a refactor. Can traverse inbound (callers), outbound (what it calls), or both.

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": "<symbol>"
    },
    "name": "injector_blast_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesThe exact symbol name to analyze.
directionNoTraversal direction: 'inbound', 'outbound', or 'both' (default: 'inbound').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.2

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. States it finds dependencies and can traverse directions, but does not mention what 'dependencies' includes (e.g., direct/transitive), performance, or side effects.

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 sentences, no fluff, front-loaded with purpose. Every sentence adds value.

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?

Adequate for two parameters with no output schema. Covers basic behavior and direction options, but could specify return format or error handling.

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 provides 100% coverage with descriptions for both parameters. Description adds context on traversal directions but does not significantly enhance semantics beyond schema.

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?

Description uses specific verb 'finds dependencies' and resource 'specific symbol', clearly stating purpose for refactoring impact analysis. Distinguishes from siblings by specifying traversal directions.

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?

Explicitly states when to use (analyzing refactor impact) and traversal options. Lacks guidance on when not to use or alternative sibling 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