Skip to main content
Glama

Get cost autopilot

get_cost_autopilot
Read-only

Read the organisation's cost autopilot policy: how much Ankra may do about cost unasked. Returns the tier each environment kind (production, staging, development, preview, unknown) defaults to, the four tiers with what each lets Ankra do on its own and what it proposes instead, the quiet hours, the notification route kept with the policy (no notice is sent to it today), and every live cluster of the current project - or of one project, or the whole organisation, with project_id - with its tier, whether an override or its environment set it, and the sentence its savings cards show. scope says what was read; partial true means RBAC hid clusters. An organisation that never set a policy reads is_set false and Hands-off everywhere. Read-only; read this before update_cost_autopilot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cost_autopilot"
  }
}

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.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description goes well beyond that: it discloses that 'partial true means RBAC hid clusters', that an unconfigured org returns is_set false with Hands-off everywhere, and that the stored notification route receives no notices today. These are non-obvious edge-case behaviors an agent could not infer from annotations or schema.

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

Conciseness3/5

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

The purpose is front-loaded, but the body is one very long run-on sentence stacking tier semantics, cluster fields, savings-card text, scope and partial flags. Every element earns its place given the missing output schema, yet breaking it into structured clauses would improve scanability considerably.

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?

With no output schema, the description must carry the return shape, and it does: tier defaults per environment kind, the four tiers' autonomous vs proposed actions, quiet hours, notification route, and per-cluster tier/provenance/savings text. It also covers the RBAC-truncation and never-configured cases, leaving no significant gap for a one-parameter read tool.

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 coverage is 100% and the project_id description already documents the 'all' value and the default conversation-scoped behavior. The description only restates the scope options ('or of one project, or the whole organisation, with project_id') without adding syntax or format detail, so the baseline 3 applies.

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 specific verb and resource ('Read the organisation's cost autopilot policy') and immediately characterizes what the resource governs ('how much Ankra may do about cost unasked'). It also names the sibling it complements ('read this before update_cost_autopilot'), so the agent can place it among the many get_* tools without opening schemas.

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 a clear call-to-action sequence relative to update_cost_autopilot ('read this before...') and the project_id paragraph in the schema explains scope selection (single project, whole org, or conversation default). It does not state when the tool is unnecessary, but the read-before-write guidance is explicit and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.