Skip to main content
Glama

amberflo

by io.usefulapi

Get all usage

amberflo_get_all_usage
Read-only

Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_time_in_secondsNoRange end, unix epoch seconds. Defaults to now if omitted.
group_by_customer_idNoWhen true, group results by customer (sends groupBy=customerId).
filter_by_customer_idNoRestrict results to a single customerId.
start_time_in_secondsYesRange start, unix epoch seconds (inclusive).
time_grouping_intervalYesBucket size: HOUR | DAY | WEEK | MONTH.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true. Description adds only the HTTP method (GET) which is consistent. No additional behavioral details (e.g., pagination, limits, rate limits) are provided beyond annotations.

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 sentences only, no wasted words. Clear and efficient. Essential information is front-loaded.

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?

No output schema, but description does not hint at the return format (e.g., structure, pagination). For a tool returning aggregated usage across all meters, more context about output would be helpful. Incomplete for a tool with no output schema.

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%; each parameter is already well-described. Description adds minimal extra context by mentioning optional grouping/filtering, but does not elaborate on format or constraints beyond the schema.

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?

Description clearly states the tool gets total usage across all meters over a time range, with optional grouping/filtering. Verb 'get' and resource 'total usage across all meters' are specific. Distinguishes from siblings like 'amberflo_get_usage' which likely targets a single meter.

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?

Implies usage for aggregated metrics across all meters, but lacks explicit when-to-use or when-not-to-use compared to alternatives like 'amberflo_get_usage' or 'amberflo_explain_usage'. No exclusions or context for selection.

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

All amberflo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool targets a distinct action and resource (e.g., create_customer vs list_customers, get_customer_plan vs list_customer_plan_history). No two tools overlap in purpose; descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow the consistent pattern amberflo_verb_noun with snake_case. Verbs like create, get, list, assign, explain, ingest are used uniformly, and nouns consistently represent the resource (customer, usage, meters, etc.).

Tool Count5/5

14 tools is well-scoped for a billing/metering server, covering customer management, plan assignment, invoices, usage ingestion/querying, and meter discovery. Each tool serves a clear purpose without excess.

Completeness4/5

The tool set covers essential CRUD and lifecycle operations for customers, plans, invoices, and usage. Minor gaps exist (e.g., no update or delete customer, no unassign plan), but the core workflows are fully supported.

Resources