Skip to main content
Glama
mguttmann
by mguttmann

Getting report errors

action1_list_report_errors
Read-onlyIdempotent

Retrieve errors from a specific report. Use this to identify and address issues in report data.

Instructions

Getting report errors. Returns report errors for the specified report. Perm: view_reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoProvide the number of the first record to be returned.
limitNoSet the maximum number of items to be returned (the page size).
cursorNoPagination cursor.
filterNoProvide a case-insensitive substring to filter and narrow down returned results (i.e., if...
org_idNoOrg UUID.
sortbyNoDefine the sorting order by a certain field.
verboseNoSkip per-item compactor.
report_idYesProvide a specific report ID.
auto_paginateNoWalk all pages.
response_formatNoOutput format. Default markdown.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countYes
itemsYes
totalNo
has_moreNo
next_cursorNo
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint; the description adds the permission requirement 'Perm: view_reports', which is useful context beyond annotations. 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.

Conciseness4/5

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

The description is very concise with two sentences, front-loading the purpose. However, the first sentence is slightly redundant with the second.

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?

Given the output schema exists, the description is adequate but could be more complete by explaining how this tool differs from similar list tools (e.g., list_report_data).

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 the schema already documents all parameters. The description does not add additional parameter-level meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the verb 'Getting' and resource 'report errors', and specifies 'for the specified report', distinguishing it from siblings like list_report_data or list_reports.

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?

The description mentions a required permission 'Perm: view_reports', but does not provide explicit guidance on when to use this tool versus alternatives, nor when not to use it.

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/mguttmann/action1-mcp'

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