Skip to main content
Glama

Per-Tool Usage Breakdown

account.analytics.tools
Read-onlyIdempotent

Analyze tool usage with breakdowns of calls, cost, cache hits, and latency. Sort by cost, calls, or latency to identify most-used and most-expensive tools.

Instructions

Get per-tool usage breakdown — calls, cost, cache hits, average latency, last used. Sort by cost (highest spend), calls (most used), or latency (slowest). Identify your most-used and most-expensive tools. Free, no charge (APIbase)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort tools by: "cost" (highest spend), "calls" (most used), or "latency" (slowest). Default: "calls"calls
limitNoMax number of tools to return (1-100). Default: 20

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.

Schema Changelog

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

  1. Addedv1.5.0
  2. Removedv1.0.20
  3. Addedv1.0.17

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it is 'Free, no charge', which is not in annotations, providing marginal extra transparency. No contradictions.

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?

Description is two efficient sentences, front-loading the purpose and key features. No superfluous text.

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?

Given the tool's simplicity (2 optional params, full schema coverage, and output schema), the description covers the main functionality. However, it omits mention of the default limit (20) and that results are sorted by the specified field, which are implied but not explicit.

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?

Input schema has 100% coverage for both parameters (sort and limit) with clear descriptions. The description only restates the sort options without adding new semantics beyond the schema, so baseline score of 3.

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 clearly states the action ('Get per-tool usage breakdown') and lists the metrics returned (calls, cost, cache hits, latency, last used). It also mentions sorting options. However, it does not explicitly differentiate from sibling tools like account.analytics.timeseries or account.analytics.usage.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies it's for identifying most-used/expensive tools but lacks context for when to choose it over other analytics endpoints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server