Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Cost Alert

delimit_cost_alert
Destructive

Create, list, delete, or toggle spending threshold alerts to get notified when cloud costs exceed a configured ceiling.

Instructions

Manage cost alert rules (CRUD on spending thresholds) (Pro).

When to use: to configure ongoing spend thresholds and notifications that fire when costs exceed a configured ceiling. When NOT to use: for one-shot cost analysis (use delimit_cost_analyze) or finding optimisations (delimit_cost_optimize).

Sibling contrast: delimit_cost_analyze finds drivers; delimit_cost_optimize finds reductions; this manages the alerting layer.

Side effects: action="create"/"delete"/"toggle" write to the file-based alert store. action="list" is read-only.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAlert name. Required for create.
actionNoOne of "list" (default), "create", "delete", "toggle".list
alert_idNoExisting alert id. Required for delete/toggle.
thresholdNoCost threshold in USD. Required for create.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.7.9
    • changedInput schema / properties / action / description
      Previous value: -"Action (list/create/delete/toggle)."New value: +"One of \"list\" (default), \"create\", \"delete\", \"toggle\"."
    • changedInput schema / properties / alert_id / description
      Previous value: -"Alert ID (required for delete/toggle)."New value: +"Existing alert id. Required for delete/toggle."
    • changedInput schema / properties / name / description
      Previous value: -"Alert name (required for create)."New value: +"Alert name. Required for create."
    • changedInput schema / properties / threshold / description
      Previous value: -"Cost threshold in USD (required for create)."New value: +"Cost threshold in USD. Required for create."
  2. Changed4 schema fields changedv4.5.5
    • addedInput schema / properties / action / description
      Added value: +"Action (list/create/delete/toggle)."
    • addedInput schema / properties / alert_id / description
      Added value: +"Alert ID (required for delete/toggle)."
    • addedInput schema / properties / name / description
      Added value: +"Alert name (required for create)."
    • addedInput schema / properties / threshold / description
      Added value: +"Cost threshold in USD (required for create)."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description clearly discloses that create/delete/toggle actions write to a file-based alert store while list is read-only, which adds meaningful behavioral detail beyond the write/destructive annotations. It also states the Pro license prerequisite and the unlicensed error response, giving the agent an accurate expectation of side effects and failures.

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 with clear headings, front-loaded purpose, and no filler. Each section earns its place: usage guidance, sibling contrast, side effects, and prerequisite are all present without unnecessary elaboration.

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?

The description covers the key contextual aspects: what the tool does, when to use it, how it differs from siblings, side effects, and licensing requirements. An output schema exists, so the description does not need to explain return values, and nothing essential is missing for an agent to invoke it correctly.

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?

The input schema already provides 100% description coverage for all four parameters, including which are required for which action, so the description does not need to repeat those details. The description adds useful action-level context (list/create/delete/toggle and their side effects) but no deeper per-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 states a specific verb ('Manage') and a precise resource ('cost alert rules'), explicitly covering CRUD on spending thresholds. It distinguishes itself from the sibling tools delimit_cost_analyze and delimit_cost_optimize by defining what it does versus what they do.

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 description gives explicit 'When to use' and 'When NOT to use' guidance, naming the correct alternatives for one-shot cost analysis and optimization. The sibling contrast section further clarifies the decision boundary, leaving no ambiguity about when this tool is the right choice.

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