Skip to main content
Glama
mguttmann
by mguttmann

Getting diagnostic logs

action1_list_logs
Read-onlyIdempotent

Retrieve diagnostic logs from endpoints with pre-filtering by level, pagination, and sorting. Supports markdown or JSON output.

Instructions

Getting diagnostic logs. Gets diagnostic logs. Use parameters to pre-filter returned results. Perm: manage_endpoints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoProvide the number of the first record to be returned.
levelNoSpecify the minimum request level.
limitNoSet the maximum number of items to be returned (the page size).
cursorNoPagination cursor.
org_idNoOrg UUID.
sortbyNoDefine the sorting order by a certain field.
verboseNoSkip per-item compactor.
auto_paginateNoWalk all pages.
response_formatNoOutput format. Default markdown.

Output Schema

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

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description adds some value by including 'Perm: manage_endpoints.' However, it does not disclose pagination behavior or rate limits.

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

Conciseness3/5

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

The description is short but contains redundancy ('Getting diagnostic logs' repeated). It could be condensed into one clear sentence without loss of 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?

With an output schema present and annotations covering safety, the description is minimally acceptable. However, given the broad concept of 'logs' and many parameters, more context about log types or sources would improve completeness.

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?

All 9 parameters have descriptions in the input schema (100% coverage). The description's mention of pre-filtering is already implied by the schema, so no additional meaning is added.

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 redundantly states 'Getting diagnostic logs. Gets diagnostic logs.' It does not specify what kind of diagnostic logs or their source, making it vague. Compared to siblings like 'action1_list_audit_events', the distinction is unclear.

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?

No guidance is provided on when to use this tool versus alternatives like other list tools. The statement 'Use parameters to pre-filter returned results' is generic and does not differentiate from sibling tools.

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