Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Cost Analyze

delimit_cost_analyze
Read-onlyIdempotent

Find cost drivers in your project by scanning Dockerfile, dependency manifests, and cloud configs to pinpoint where spending originates.

Instructions

Analyze a project for cost drivers (Dockerfile, deps, cloud) (Pro).

When to use: when investigating spend on a project — scans Dockerfile, dependency manifests, and cloud configs for cost signals. When NOT to use: to enact cost reductions (use delimit_cost_optimize) or to manage alert rules (delimit_cost_alert).

Sibling contrast: delimit_cost_optimize finds reduction opportunities; this surfaces drivers (where the cost is).

Side effects: read-only on the target. Gated by require_premium. Calls backends.tools_data.cost_analyze.

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoProject or infrastructure path to analyze. Default "." (cwd)..

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.7.9
    • changedInput schema / properties / target / description
      Previous value: -"Project or infrastructure path to analyze."New value: +"Project or infrastructure path to analyze. Default \".\" (cwd)."
  2. Changed1 schema field changedv4.5.5
    • addedInput schema / properties / target / description
      Added value: +"Project or infrastructure path to analyze."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description states the target is scanned read-only, that the tool is gated by require_premium, that it calls a specific backend function, and that an unlicensed call returns an upgrade payload without executing. This gives the agent a clear model of side effects and failure behavior.

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 more verbose than minimal but remains well structured with labeled sections and a front-loaded summary. There is minor redundancy between 'Gated by require_premium' and the later 'Prerequisite' sentence, so it is not perfectly concise.

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 simple one-parameter, read-only analysis tool with an output schema, the description covers purpose, usage boundaries, prerequisites, side effects, and unlicensed behavior. Nothing essential for calling 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?

With 100% schema description coverage, the schema already documents target and its default. The description adds some context about what the scan looks for (Dockerfile, dependency manifests, cloud configs), but it does not introduce substantial new parameter semantics beyond the 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?

The description opens with a specific verb and resource: 'Analyze a project for cost drivers (Dockerfile, deps, cloud)'. It later contrasts with delimit_cost_optimize and delimit_cost_alert, making it easy to distinguish this tool from the most relevant siblings.

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?

The 'When to use' section gives a concrete investigation scenario, and 'When NOT to use' explicitly routes to delimit_cost_optimize and delimit_cost_alert. This is unambiguous selection guidance.

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