Skip to main content
Glama

list_revenue_reports

Read-only

List revenue reports

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_revenue_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered, but the description adds nothing beyond them: no indication of how many reports are returned, pagination, ordering, or whether results are scoped to the current user/workspace. With annotations carrying the structural burden, this minimal restatement leaves a real behavioral gap.

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

Conciseness2/5

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

Three words, front-loaded and free of noise, but the brevity is under-specification rather than economy — the single sentence conveys no information beyond the tool identifier. Nothing is wasted, yet nothing is earned.

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 zero-parameter, read-only list tool the description could be complete, but with no output schema and no statement of what a revenue report contains or how results are bounded, an agent cannot predict the response shape or cost. Against a crowded family of ~45 sibling reporting tools, this is not enough to call it correctly with confidence.

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?

The tool takes zero parameters, so the baseline is 4; the schema is empty and 100% covered by definition. Nothing in the description is needed to compensate, though the description also does not mention that the call is unfiltered.

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

Purpose2/5

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

The description is a direct restatement of the tool name ('list_revenue_reports' -> 'List revenue reports'), adding no scope, no filtering, and no distinction from the many sibling list tools (list_reports, list_session_reports, list_retention_reports, etc.). An agent gets only the tautology that this lists revenue reports.

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 when-to-use guidance, no mention of alternatives such as get_revenue_report (singular, likely fetching one report) or the generic list_reports, and no prerequisites or exclusions. The agent must infer the routing decision entirely from the name.

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