Skip to main content
Glama

run_kit

Execute a composable kit workflow — combining modes like explore, deep dive, or code review — to analyze a codebase within a token budget.

Instructions

Run a composable kit — a named multi-mode workflow that combines tempograph modes into a single token-budgeted response.

kit: name of the kit to run, or "list" to show all available kits.
  Built-in kits:
    explore     — overview + hotspots (orient to a new codebase)
    deep_dive   — focus + blast (deep-dive into a symbol)
    change_prep — diff + focus (prepare for a code change)
    code_review — dead + hotspots + focus (code review workflow)
    health      — hotspots + dead (codebase health check)
  Custom kits can be defined in .tempo/kits.json.
query: optional symbol or topic for focus/blast steps
max_tokens: total token budget across all kit steps (default 4000)
exclude_dirs: comma-separated directory prefixes to skip
output_format: "text" (default) or "json"

Examples:
- run_kit(".", "explore")                         → overview + hotspots
- run_kit(".", "deep_dive", query="render_focused") → focus + blast on symbol
- run_kit(".", "health")                          → hotspots + dead code
- run_kit(".", "list")                            → show all available kits

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathNo/demo
kitNo
queryNo
max_tokensNo
exclude_dirsNo
output_formatNotext

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses that the tool combines modes with a token budget and supports output formats. It does not mention side effects, authentication requirements, or read-only nature. The token-budget detail adds value but gaps remain.

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

Conciseness4/5

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

The description is structured with a clear opening sentence, bullet list of built-in kits, and examples. It is slightly verbose but front-loaded effectively. Every sentence adds value, though some redundancy exists in listing examples.

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 presence of an output schema, the description does not need to detail return values. It covers parameter usage, built-in kits, and examples. Missing is guidance on error cases (e.g., invalid kit name) and how custom kits are defined, but overall it is sufficient.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It explains the 'kit', 'query', 'max_tokens', 'exclude_dirs', and 'output_format' parameters with context and examples. However, 'repo_path' is only listed in the schema with a default and no explanation, leaving a minor gap.

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 the tool's purpose: 'Run a composable kit — a named multi-mode workflow'. It distinguishes from sibling tools by positioning it as a workflow combiner rather than a single mode. Built-in kits and examples reinforce specificity.

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 clear context on when to use the tool (to run predefined workflows) and includes an option 'list' to discover kits. However, it does not explicitly state when not to use it or suggest alternatives like individual mode tools.

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