Skip to main content
Glama

Ankra

by ai.ankra
OverviewDiscussionsAdmin

set_cost_budget

Create a monthly cost budget, or change one. To create, give name, scope_kind (organisation, project, cluster, environment or application), scope_id (the project, cluster or application id, or the environment label; omit for the organisation), monthly_amount in whole units of currency, and currency; a scope holds one budget. To change, give budget_id and only the fields that change - the scope never changes, the rest keeps its value, and owner_user_id null or clear_owner true clears the owner. notify_at_pct (default 80) is the share of the budget at which its card is raised. Organisation admins only (billing.manage); every change is audited. Reversible by setting the previous values back (read get_cost_budgets first).

Input Schema

NameRequiredDescriptionDefault
nameNo1 to 120 characters.
currencyNousd, eur, gbp, sek, nok, dkk, chf, pln, czk, jpy, cad, aud or inr.
scope_idNoThe project, cluster or application id, or the environment label; omit for the organisation. Only on a create.
budget_idNoThe budget to change; omit to create one.
scope_kindNoWhat the budget covers; only on a create. A project budget covers the clusters the project holds now.
clear_ownerNoClear the owner on a change.
notify_at_pctNoRaise the budget's card when the projection reaches this percent of the budget. Defaults to 80 on a create.
owner_user_idNoAn active member of the organisation the budget is for; null clears.
monthly_amountNoThe budget per month in whole units of currency, like 5000 for 5,000 EUR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / scope_id / description
      Previous value: -"The cluster or application id, or the environment label; omit for the organisation. Only on a create."New value: +"The project, cluster or application id, or the environment label; omit for the organisation. Only on a create."
    • changedInput schema / properties / scope_kind / description
      Previous value: -"What the budget covers; only on a create."New value: +"What the budget covers; only on a create. A project budget covers the clusters the project holds now."
    • changedInput schema / properties / scope_kind / enum
      Previous value: -[
-  "organisation",
-  "cluster",
-  "environment",
-  "application"
-]New value: +[
+  "organisation",
+  "project",
+  "cluster",
+  "environment",
+  "application"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (non-readonly, non-idempotent, non-destructive), it discloses that the scope is immutable on change, unlisted fields retain their values, owner clearing happens via null or clear_owner, notify_at_pct defaults to 80, every change is audited, and changes are reversible. This is materially more than the structured fields provide.

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?

Front-loaded with the core action, then organized by create/change path with no filler. It is dense and long, but nearly every clause adds operational detail (permissions, defaults, reversibility) rather than restating the schema.

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 9-parameter mutation tool with no output schema, the description supplies the mode logic, required fields, permission gate, default value, and rollback path an agent needs to call it safely. Nothing critical is missing.

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 coverage is 100%, so per-parameter meaning is already documented and the baseline would be 3. The description earns extra credit by explaining how parameters combine into modes (create vs change field sets), the 'a scope holds one budget' constraint, and the omit-for-organisation rule that no single schema field conveys.

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 opening sentence states a specific verb pair and resource: 'Create a monthly cost budget, or change one.' It cleanly distinguishes this tool from siblings like get_cost_budgets (read) and delete_cost_budget, and names get_cost_budgets explicitly as the read counterpart.

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?

It spells out exactly when to create versus change, which fields each mode needs and which are ignored, and points the agent at get_cost_budgets before modifying. Prerequisites (billing.manage, organisation admins) are stated up front rather than left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ankra toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources