Skip to main content
Glama

Get Sonilo usage

get_usage
Read-onlyIdempotent

Retrieve the authenticated account's usage summary and per-day breakdown to reconcile costs and track generation history; set a lookback window of 1–365 days (default 30).

Instructions

Get the authenticated account's usage summary and per-day breakdown. Useful for cost reconciliation and tracking generation history.

Args: days (int, optional): Lookback window in days, 1–365. Defaults to 30.

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
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/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 genuinely new behavioral facts beyond that: results are scoped to the authenticated account and the payload contains both a summary and a per-day breakdown. It does not mention pagination, rate limits, or how empty usage periods are represented, keeping it short of 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 front-loaded sentences state purpose and use case, followed by a compact Args block that adds range information not present in the schema. Every element earns its place; nothing is restated from structured fields.

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 zero-required-parameter read-only tool, the description covers purpose, use case, account scoping, return shape (summary plus per-day breakdown), and the full semantics of the one argument. Without an output schema, more detail on the exact fields of the breakdown would help, but an agent has everything needed to call it correctly.

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

Parameters5/5

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

Schema description coverage is 0% and the schema gives only a bare integer with a default, so the description carries the full burden — and it does: the single parameter is optional, typed int, bounded 1–365, defaults to 30, and its meaning (lookback window) is spelled out. No ambiguity remains for the caller.

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?

States a specific verb and resource: fetching the authenticated account's usage summary with a per-day breakdown. This is unmistakable against all siblings, which are generation/processing tools, though no sibling is named explicitly. The scope ('authenticated account's') is a valuable qualifier that avoids ambiguity about whose usage is returned.

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

Usage Guidelines4/5

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

Gives concrete contexts where the tool applies: cost reconciliation and tracking generation history. That is enough for an agent to recognize the trigger, but no exclusions or alternatives are stated, and there is no guidance on what to do if the lookback window needs to exceed 365 days.

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