Skip to main content
Glama

Show this month's spend per server

getMonthSpending
Read-onlyIdempotent

Breaks this calendar month's spend so far down by server: cost, compute cost, data sent to players and time awake. Match each serverId to a name with listServers and name servers by that name. For the total and the balance use getBalance.

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": "getMonthSpending"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior beyond them by pinning the window to 'this calendar month's spend so far,' telling the agent the figures are partial-month rather than a completed billing period. It does not mention units/currency or ordering, which keeps it from a 5.

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?

Two tight sentences: the output breakdown is front-loaded, then the follow-up calls are named. Every clause carries information an agent needs, with no repetition of the title or annotations.

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?

With no parameters and no output schema, the description carries the burden of describing the return shape and does so by listing the four measured dimensions. It names the ID-to-name join step, which prevents a common misuse. Minor gaps remain on units/currency and whether results are sorted or limited.

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?

The tool takes zero parameters, so there is no schema semantics to add beyond what exists. The description correctly spends no words on parameters and instead documents the returned breakdown, which is the right use of space for a no-arg tool.

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 ('Breaks this calendar month's spend so far down by server') and enumerates the exact output dimensions: cost, compute cost, data sent to players, time awake. It is clearly distinguishable from getBalance, which is named as the tool for totals and balance.

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?

Explicitly routes the agent: use listServers to map serverId to a name, and use getBalance for the total and balance instead of this tool. Both alternatives are named with the condition that selects them, and the implicit scope (this calendar month only) is stated up front.

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