Skip to main content
Glama

reports_list

Read-onlyIdempotent

Your report library: every analysis delivered, with status and links. Pass semantic_query to search report content in plain language. A delivered package is read with package_status and my_objects.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
semantic_queryNoNatural-language search over your reports' content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds that entries carry status and links, but says nothing about ordering, pagination behavior for the limit parameter, or how semantic search ranks/filters results.

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?

Compact and front-loaded: the resource identity comes first, then the search hint, then the sibling routing. The final sentence ('A delivered package is read with package_status and my_objects') is slightly oblique in wording but earns its place as routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A two-parameter read tool with full annotations and no output schema: the description covers purpose and search use, but leaves the return shape (beyond 'status and links'), default limit of 10, and result ordering unaddressed. Adequate but with visible gaps given the absence of an output schema.

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% and both parameters are already documented, including 'Natural-language search over your reports' content'. The description's semantic_query sentence largely restates the schema, adding no syntax, ranking, or limit-interaction details, so 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?

States the resource and scope explicitly: 'Your report library: every analysis delivered, with status and links.' That is a clear verb-less but specific read of a list resource, and it distinguishes itself from report-detail siblings by routing to package_status/my_objects. It does not, however, explicitly contrast with reports_view or report_cards.

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 a concrete trigger for the search path ('Pass semantic_query to search report content in plain language') and names where to go instead for a delivered package (package_status, my_objects). It stops short of stating when to just list versus search, or when to prefer reports_view for a single report.

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.