Skip to main content
Glama

ADS Beast

list_reports

Read-only

Return the client reports already generated in ADS Beast, newest first, with their type, period and client.

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

Input Schema

NameRequiredDescriptionDefault
limitNoReports per page, newest first. Each report carries its sections, so keep pages small.
offsetNoReports to skip; use next_offset from the previous page.
client_idNoRestrict to one client.
report_typeNoRestrict to one kind of report, for example monthly or audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds ordering ("newest first") and the fields returned (type, period, client), which is real added context, but it says nothing about volume, whether the list is scoped to the caller's clients, or what an empty result means.

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 or redundancy. It is efficient, though it is short enough that it could have carried one more sentence of guidance without becoming bloated.

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 read-only list tool with full schema coverage and safety annotations, the description covers purpose, ordering, and returned fields. Missing only minor items such as pagination cues (left to the schema) and expected result volume.

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 coverage is 100%, so limit, offset, client_id and report_type are already fully documented in the schema. The description only reinforces the newest-first ordering that limit's schema text mentions, adding no new meaning; baseline 3 applies.

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 gives a specific verb and resource ("Return the client reports already generated") and states the scope is existing generated reports, which cleanly separates it from creation or listing of clients/campaigns. It does not name or contrast any specific sibling, so it stops short 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 Guidelines3/5

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

Use is implied by "already generated" (i.e., fetch prior output rather than trigger generation), but there is no explicit when-to-use vs when-not statement and no named alternative for related needs. Adequate but leaves routing to inference.

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.