ShortsIntel

Get usage

get_usage

Read-onlyIdempotent

Use when you need what has already been paid for, before repeating work: recent charges, one per Run, with kind, status, charge and list price in Credits, plus the total. Not for the Credits left: get_balance. Not for one Run's result: get_run. Price: 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": "get_usage"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Output Schema

Name	Required	Description
`items`	No
`next_cursor`	No
`total_charged_credits`	No	Every charge on the account, not just this page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026
- changedOutput schema / properties / items / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / items / items / properties
```
Removed value: -{}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_charged_credits": {
+      "description": "Every charge on the account, not just this page.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real context beyond them: the result shape (one charge per Run with kind/status/charge/list price plus a total) and the cost model ('Price: Free'). It omits how paging behaves when more charges exist than the limit, 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?

Three short sentences, trigger first, then exclusions, then cost. Every clause is load-bearing and there is no filler or repetition of the title.

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

Completeness3/5

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

The output schema exists, so return fields need not be explained, and the read-only nature is handled by annotations. However, for a paginated list tool with an undocumented cursor and a capped limit, the description leaves an agent guessing how to iterate past the first page — a meaningful gap in an otherwise solid definition.

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% and neither parameter is described in the schema, so the description carries the full burden. It never mentions 'limit' or 'cursor' — neither their bounds (1-100), their defaults, nor how cursor paging interacts with 'recent charges'. The word 'recent' hints at a default window but adds no actionable meaning.

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 plus the exact payload: 'recent charges, one per Run, with kind, status, charge and list price in Credits, plus the total.' It also names what the tool is not (get_balance, get_run), so an agent can separate it from siblings without opening schemas.

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?

Gives an explicit trigger ('when you need what has already been paid for, before repeating work') and two explicit exclusions routing to the correct alternatives: get_balance for remaining Credits, get_run for a single Run's result. When-to-use and when-not-to-use are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ShortsIntel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?