Skip to main content
Glama

usage_summary

Read-onlyIdempotent

Get account usage totals, owned-project count, limits, and aggregate database/file storage with no arguments. Project AI calls and costs exclude Advisor calls, which are accounted separately. From this change onward, new release-based production publications count once on successful completion, excluding previews, dry runs, unchanged deploys, rollbacks and retries. Historical counters retain their original meaning.

view: "projects" returns a bounded page of owned-project details (default 20, maximum 100); the returned cursor fetches the next page. Account totals remain account-wide. Passing project_id or period uses the historical usage call (deploys, project AI calls/costs, emails), without storage or pagination.

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

Input Schema

NameRequiredDescriptionDefault
viewNoDefault account totals; projects requests a bounded detail page.
limitNoProject detail page size (default 20).
cursorNoNext project-page cursor returned by usage_summary.
periodNoTime period, e.g. "7d", "30d" (default: 30d)
project_idNoOptional. Accepts UUID, subdomain, or 'default'. Omitted: all projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: explains Advisor-call exclusion, counting semantics for publications (excludes previews, dry runs, unchanged deploys, rollbacks, retries), pagination via returned cursor, and that project_id/period switch to a call lacking storage. This is exactly the kind of edge-case detail annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The mode/pagination semantics are useful, but the sentences 'From this change onward…' and 'Historical counters retain their original meaning' read as changelog/versioning noise of questionable relevance to invocation. The core usage guidance is also pushed behind that migration paragraph, hurting front-loading.

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 5-param, mode-switching read tool with no output schema, the description covers modes, pagination, and counting semantics well. What is missing is any hint of the returned totals structure, though with a clear read-only profile and no output schema this gap is minor.

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

Parameters4/5

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

Schema coverage is 100% so baseline is 3, but the description adds cross-parameter meaning the schema cannot: that project_id OR period triggers the historical usage path, and that view:projects defaults to 20 with a 100 max and account totals staying account-wide. This is genuine added value over the field-level schema.

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?

Opens with a specific verb and resource set: 'Get account usage totals, owned-project count, limits, and aggregate database/file storage.' This is clearly distinguishable from data-mutation or query siblings. It does not explicitly name an alternative tool, keeping it just shy 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 Guidelines4/5

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

Gives concrete conditional routing: default account view vs `view: "projects"` for a paginated detail page, and states that passing `project_id` or `period` invokes the historical usage call (deploys, AI calls/costs, emails) without storage/pagination. Strong in-tool guidance, though it stops short of naming sibling tools like ai_usage or advisor for exclusion cases.

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