Skip to main content
Glama

list_usage_reports

Read-only

Read recent, self-reported use by task, item, or runtime.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
limitNoResults per page. Default: 5.
cursorNoPass the previous next_cursor back unchanged.
item_idNo
runtimeNo
versionNo
deliveryNo
initiationNo
evaluation_basisNo

Output Schema

NameRequiredDescriptionDefault
basisYes
itemsYes
next_cursorYes
window_daysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: results are time-limited ('recent') and the data is user-declared rather than measured ('self-reported'), which affects how an agent should trust the numbers. It omits pagination behavior, default page size, ordering, and whether empty results are an error.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing detail noted elsewhere.

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?

For a 9-parameter, fully optional-filter list tool with three enum dimensions, one short sentence is insufficient. The output schema covers return values, but the description should still explain what the enum filters select and how the cursor/limit paging works; neither is addressed.

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 only 22% across 9 parameters, so the description must carry the explanation burden, and it barely does. It names item and runtime filtering but says nothing about tag, version, delivery, initiation, or evaluation_basis, nor about how limit and cursor interact for paging.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Read' plus the resource 'recent, self-reported use' identifies a read/list operation, and 'by task, item, or runtime' hints at the available groupings. However, 'use' and 'usage report' are left undefined, and the wording is close enough to the sibling 'report_usage' that an agent could confuse reading past usage with submitting new usage. 'Recent' is never quantified.

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?

There is no statement of when to use this tool versus 'report_usage' or 'list_audit_events', and no prerequisites or exclusions are given. The agent must infer from the verb alone that this is the retrieval counterpart to reporting usage.

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