Skip to main content
Glama

miro_get_audit_log

Read-only

Query the local audit log to monitor MCP tool executions. Filter by time range, tool, board, action type, or success status to track usage and troubleshoot issues.

Instructions

Query local audit log for MCP tool executions (this session only). Filter by time range, tool, board, action type, or success/failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoFilter by tool name (e.g., miro_create_sticky)
limitNoMaximum events to return (default 50, max 500)
sinceNoReturn events after this time (ISO 8601, e.g., 2024-01-01T00:00:00Z)
untilNoReturn events before this time (ISO 8601, e.g., 2024-01-02T00:00:00Z)
actionNoFilter by action type: create, read, update, delete, export, auth
successNoFilter by success status (true/false)
board_idNoFilter by board ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
eventsYes
messageYes
has_moreYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds the session scope, which is valuable behavioral context. No contradiction.

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

Conciseness5/5

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

Single, well-structured sentence front-loading the verb and resource. No wasted words.

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?

Description covers the purpose, scope, and filterable fields. With an output schema present, the lack of return format details is acceptable. The session-scope is clearly highlighted.

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% with descriptions for all 7 parameters. The description only rephrases the filter options already present in the schema, adding no new semantic insight.

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?

Description clearly states the verb 'Query' and the resource 'local audit log for MCP tool executions' with scope 'this session only'. No sibling tool has a similar audit function, so it is well-distinguished.

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?

The description explicitly states the scope ('this session only'), which helps the agent understand it is for local debugging. It does not provide when-not-to-use or alternatives, but since no other sibling is an audit tool, the lack of exclusion is acceptable.

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/olgasafonova/miro-mcp-server'

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