Skip to main content
Glama
Elmoaid

TempoGraph

by Elmoaid
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

blast_radius

Identify what breaks when changing a file or symbol. Shows importers, callers, and dependency chains across languages.

Instructions

What breaks if you change this file or symbol? Shows importers, external callers, component render chains, and cross-language bridges.

Parameter priority: if BOTH file_path and query are provided, query wins.
- file_path: whole-file blast radius, e.g. "src/lib/db.ts"
- query: symbol-level blast radius (more precise), e.g. "Sparkline.max"
For large monolith files, prefer query over file_path.
At least one of file_path or query must be provided.

output_format: "text" (default) or "json" for structured response

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathNo/demo
file_pathNo
queryNo
exclude_dirsNo
output_formatNotext

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

No annotations require full burden on description; it reveals parameter priority, required-parameter condition, and output options. However, it lacks details on authorization or rate limits, though these are less critical for a read-only analysis tool.

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 uses bullet points and parameter lists effectively, is free of fluff, and front-loads the core 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?

Given the tool's complexity, the description covers purpose, usage scenarios, parameter dependencies, and output format. It could mention response size or async behavior, but existing output schema supplements return values.

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?

With 0% schema coverage, the description explains file_path and query well, and mentions output_format, but leaves repo_path and exclude_dirs unexplained. This is partial compensation for the low coverage.

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 'What breaks if you change this file or symbol?' and details specific impact types (importers, external callers, etc.), making the tool's purpose unambiguous and distinct from siblings.

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 provides explicit guidance on when to use file_path vs query and prefers query for large files, but does not compare with sibling tools like 'dependencies' or 'cochange_context'.

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/Elmoaid/TempoGraph'

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