Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Impact

delimit_impact
Read-onlyIdempotent

Assess the blast radius of an API change by scanning dependency manifests for callers. Get an informational impact report on downstream effects before planning your change.

Instructions

Analyze downstream impact of an API change (informational only).

When to use: when assessing blast radius for a planned API change, by inspecting a dependency manifest for callers of the named API. When NOT to use: to make a gate decision (use delimit_lint or delimit_gov_evaluate for pass/fail) — this returns information.

Sibling contrast: delimit_lint returns pass/fail; this returns a blast-radius report.

Side effects: read-only. Calls backends.gateway_core.run_impact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_nameYesThe API name that changed. Required.
dependency_fileNoOptional path to a dependency manifest file (package.json, requirements.txt, go.mod) to scan for callers. Default None = backend default path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.7.9
    • changedInput schema / properties / api_name / description
      Previous value: -"The API that changed."New value: +"The API name that changed. Required."
    • changedInput schema / properties / dependency_file / description
      Previous value: -"Optional path to dependency manifest."New value: +"Optional path to a dependency manifest file (package.json, requirements.txt, go.mod) to scan for callers. Default None = backend default path."
  2. Changed2 schema fields changedv4.5.5
    • addedInput schema / properties / api_name / description
      Added value: +"The API that changed."
    • addedInput schema / properties / dependency_file / description
      Added value: +"Optional path to dependency manifest."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds useful context beyond annotations: it is 'informational only', not a gate decision, and it calls backends.gateway_core.run_impact. This gives the agent a clear picture of behavior without being exhaustive.

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 well-structured and front-loaded: purpose first, then usage guidance, then sibling contrast, then side effects. Every sentence serves a distinct purpose and there is no filler.

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

Completeness5/5

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

For a read-only analysis tool with rich annotations, full schema coverage, and an output schema, the description covers purpose, usage, alternatives, exclusions, and side effects. Nothing needed for an agent to select and invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents both api_name and dependency_file. The description reinforces that dependency_file is a manifest path (package.json, requirements.txt, go.mod), but this is also in the schema, so no significant extra meaning is added.

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 states a specific verb and resource: 'Analyze downstream impact of an API change', and clarifies scope via 'blast radius' and 'dependency manifest'. It also distinguishes itself from delimit_lint by noting that this returns a blast-radius report rather than pass/fail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'When to use' guidance, explicitly says 'When NOT to use', and names the exact alternatives (delimit_lint, delimit_gov_evaluate). This fully routes the agent to the correct tool.

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