Skip to main content
Glama

Visibility Genies

Read spend

get_spend_summary
Read-only

The account's balance (free to spend, or sponsored when the account manager pays) and what it was charged in a month, this month so far unless one is given, from the same wallet the Spend page reads: by feature, by project, by client and by who started the work (MCP agents, pages in the app, scheduled runs), with what is still held for work running now and, on the account's own keys, what those keys paid. For the Owner and people who manage billing, also each client's month at the client price the account set for it (its own pricing toward that client, which changes nothing it is charged), and what its budget has left when one is on. Also the agent spend limit: how much one tool call may spend without asking. Only a member with spend access can read it, within their allowed projects. Free: buys nothing.

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_spend_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoThe month to read, as YYYY-MM in UTC, as the Spend page counts months. Omit for this month so far.

Output Schema

NameRequiredDescriptionDefault
metaNo
monthYes
balanceYes
heldUsdYes
byClientYes
bySourceYes
byFeatureYes
byProjectYes
chargedUsdYes
clientPricesNo
agentSpendLimitUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare a safe read-only operation, and the description adds genuine context: role-based visibility for Owners/billing users, project-scoped access, the default current-month behavior, and the distinction between what is charged and what is merely held. It does not address rate limits or response shape, but the output schema covers the latter.

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

Conciseness2/5

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

The entire description is one roughly 100-word run-on sentence with stacked clauses, parentheticals, and repeated 'and' constructions, making it hard to scan. The information is mostly relevant, but the lack of structure and front-loaded summary beyond the opening phrase works against clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only reporting tool with an output schema, the definition covers the key contexts an agent needs: what data is included, who can see which portions, project scoping, and the default month. The cryptic closing phrase "Free: buys nothing." adds ambiguity rather than completeness, preventing a 5.

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 single month parameter has full schema coverage including pattern and description, so the schema does the heavy lifting. The description restates the default ("this month so far unless one is given") and adds only a minor pointer to how the Spend page counts months; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and the specific figures it returns (balance, month charges, per-feature/project/client/agent breakdowns, held amounts, key charges), so the purpose is unambiguous. It does not explicitly differentiate itself from sibling reporting tools such as get_project_summary or the various get_* reports, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many sibling reporting tools. The only constraints given are access-related ("Only a member with spend access..."), which is authorization context rather than usage routing.

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