Skip to main content
Glama

Billing usage analytics

spur_get_usage_analytics
Read-onlyIdempotent

Read dated usage, spend and wallet activity. Free.

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

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
group_byNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a meaningful note that the call is free (no billing impact) and that results are 'dated', but it omits what happens when start/end are omitted, the default range, and whether output is paginated. Baseline adequacy rather than richness.

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?

Two short sentences with no filler, and the core operation is front-loaded. It is arguably too terse rather than padded, so nothing needs deleting, but the second fragment ('Free.') is a sticky note rather than structure.

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

Completeness2/5

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

With three optional parameters, no output schema and zero schema description coverage, the description should explain defaults and result shape, and it does neither. An agent cannot infer what an unparameterized call returns or how the period is chosen. For an analytics read tool this leaves too much unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for start, end and group_by and largely fails to. 'Dated' gestures at a date range but does not say whether bounds are inclusive, what the default window is, or that group_by accepts only day/month and what it controls. The regex-formatted date pattern in schema gives format but no intent.

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 gives a specific verb and resource set: 'Read dated usage, spend and wallet activity.' An agent can tell this returns billing/usage data rather than performing an action. It stops short of contrasting itself with near-siblings such as spur_get_billing_summary or spur_manage_billing, so the boundary is left implicit.

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 when-to-use or when-not-to-use guidance at all. Nothing tells the agent whether to reach for this versus the billing summary tool, and no prerequisites or context are stated. The only hint is 'Free', which is informational rather than a selection rule.

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