Skip to main content
Glama

Coline

Get billing

get_billing
Read-onlyIdempotent

Shows a team workspace's plan, trial, seats (Max seats included), Kairo usage as a percentage with its reset date, the balance and extra usage spent in dollars, and whether it can invite more people. Paying and changing plans happen in Coline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "get_billing"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
planYes
seatsYes
stateYes
balanceYes
canInviteYes
kairoUsageYes
trialDaysLeftYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only, idempotent operation, and the description adds substantial context about the specific billing information returned. It does not discuss access requirements or error behavior, but it goes well beyond the safety signals provided by annotations.

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 definition is two tight sentences: the first front-loads exactly what the tool returns, and the second adds a useful scope boundary. There is no redundant wording or unnecessary setup.

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 tool with rich annotations and an output schema, the description is complete enough. It describes the returned billing dimensions and clarifies where payment actions belong, leaving no major ambiguity for invocation.

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 workspace parameter is fully documented as a slug from workspaces.list with an example. The description does not add further meaning beyond that, so the baseline score of 3 is appropriate.

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 precise verb and resource: it shows a team workspace's plan, trial, seats, usage, balance, and invitation eligibility. This is specific enough to distinguish it from unrelated getters such as get_team or get_profile without needing to inspect the schema.

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?

The description clearly establishes the read-only billing-status use case and explicitly excludes paying or changing plans by pointing those actions to Coline. It does not name alternative tools, but the boundary is clear enough for an agent to know what this tool is and is not for.

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.

Resources