Skip to main content
Glama

Ankra

by ai.ankra
OverviewDiscussionsAdmin

get_cost_budgets

Read-only

Read the monthly cost budgets in scope - the current project's, or one project's or the whole organisation's with project_id - largest first, each with its month as of now in the budget's own currency: spent so far, the projected month end at the current pace, the hour that pace crosses the budget, the percent of the budget, and where the month lands once the changes already approved or running have landed. status is under, approaching (past the notify threshold), crossing, over, or unknown - unknown means no cluster in scope is priced this month and the figures are null, which is unknown spend, not zero. Read-only; read this before set_cost_budget or delete_cost_budget.

Input Schema

NameRequiredDescriptionDefault
project_idNoUUID of a project to read, or all for the whole organisation. Leave it out to read the project the conversation or token is in (the whole organisation while the organisation has no projects). list_projects has the ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "UUID of a project to read, or all for the whole organisation. Leave it out to read the project the conversation or token is in (the whole organisation while the organisation has no projects). list_projects has the ids.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces read-only while adding genuinely new behavior: sort order (largest first), the meaning of each status value, and the critical null-vs-zero distinction for 'unknown' (no priced cluster this month means unknown spend, not zero). It does not mention pagination or result limits.

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 verb and scope, then the returned fields, then status semantics and the sibling pointer. The single long sentence is dense and every clause carries information, though the field enumeration could be tightened.

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?

There is no output schema, so the description carries the full burden of describing return values, and it does so thoroughly: the fields returned, the sort order, the status enum with the 'unknown' edge case, and the currency handling. An agent has enough to interpret results 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?

Schema description coverage is 100% and project_id is fully documented in the schema, including the 'all' sentinel and the default behaviour. The description restates the scoping options ('one project's or the whole organisation's with project_id') but adds no syntax or edge-case detail 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?

States a precise verb (Read) and resource (monthly cost budgets) plus the scoping dimension (current project, one project via project_id, or whole organisation). It is immediately distinguishable from the sibling mutators set_cost_budget and delete_cost_budget, which it names.

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?

Gives clear sequencing guidance ('read this before set_cost_budget or delete_cost_budget') and explains how project_id selects the scope, including the default when omitted. It stops short of stating when-not to use it, but the surrounding workflow is unambiguous.

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