Skip to main content
Glama

ExducerAI GPU cloud

Usage report

get_usage
Read-onlyIdempotent

What the account was charged for GPU time, object storage and the Models API over a date range, in CAD before tax. Only deployments that ran appear.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD, included. Default: today.
fromNoFirst day, YYYY-MM-DD, America/Toronto. Default: the first of the month.
groupNoday: one row per day and type. type: one row per type for the range.day
deployment_idNoOnly the GPU time of this deployment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this is a safe, read-only, idempotent, closed-world report. The description adds useful context: currency is CAD before tax, and only deployments that actually ran are included. It does not describe return granularity, pagination, or what happens with empty ranges, so it adds moderate rather than rich behavioral context.

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 tightly written sentences with no wasted wording, and the scope is front-loaded. The opening is a sentence fragment rather than a direct verb-led statement, which is a minor stylistic weakness but does not hurt comprehension.

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 fully documented optional parameters and safety annotations, the description covers what is being reported, the time scope, currency, and an important filtering caveat. It does not describe the output row structure, but the schema's grouping parameter and the absence of an output schema make that a minor gap rather than a blocking one.

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 description coverage is 100%, so the input schema already documents date bounds, defaults, grouping, and the deployment filter. The description reinforces the date-range scope and the deployment filtering implication but adds no syntax or interaction details beyond the schema. 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 states a specific resource and scope: charges for GPU time, object storage, and the Models API over a date range, in CAD before tax. That is clear enough for an agent to identify it as a usage-billing report. It does not explicitly distinguish itself from billing or storage-specific siblings, which keeps it short of 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 Guidelines3/5

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

Usage is implied by the scope: fetch account charges over a date range. The note that only deployments that ran appear is useful scoping, but the description gives no explicit when-to-use guidance or named alternative such as a billing or storage-specific report. An agent must infer the distinction from the resource names.

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