Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

search_audits

Search sidecar query audits with filters including user, query ID, database, table, and date range. Returns a search UUID for later retrieval of results.

Instructions

Search sidecar query audits with filters.

Triggers an async search and returns a search_uuid (valid 30 days). Use get_audit_results with the search_uuid to retrieve results. All filters are combined with AND logic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10000, max 100000).
offsetNoSkip this many results.
from_date_timeNoRFC3339 UTC start time (e.g. "2025-01-01T00:00:00Z").
to_date_timeNoRFC3339 UTC end time.
consuming_userNoFilter by consuming usernames (case-insensitive). Pass a single string or a list of strings.
consuming_user_emailNoFilter by consuming user emails. Pass a single string or a list of strings.
query_idNoFilter by specific query IDs. Pass a single string or a list of strings.
sidecar_idNoFilter by sidecar IDs. Pass a single string or a list of strings.
sidecar_instance_idNoFilter by sidecar instance IDs. Pass a single string or a list of strings.
table_nameNoFilter by table names. Pass a single string or a list of strings.
schema_nameNoFilter by schema names. Pass a single string or a list of strings.
database_nameNoFilter by database names. Pass a single string or a list of strings.
column_nameNoFilter by column names. Pass a single string or a list of strings.
statement_typeNoFilter by statement types. Pass a single string or a list of strings.
statement_text_containsNoCase-insensitive substring match on SQL text.
order_byNo"asc" or "desc" (default "desc").
sort_byNo"event_time" or "rows_accessed" (default "event_time").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses async behavior, uuid expiry (30 days), and AND logic for filters. It does not mention if the operation is read-only or other side effects, but it is sufficient for basic understanding.

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?

The description is very concise, front-loading the purpose and adding necessary workflow details in just three sentences with no wasted words.

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 17 parameters and an output schema, the description explains the async pattern and filter logic. However, it does not differentiate this tool from the similarly named sibling search_query_audits, which could cause confusion.

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 describes each parameter well. The description only adds that filters use AND logic, which adds minimal value 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 it searches sidecar query audits with filters. It specifies the async nature and the use of get_audit_results to retrieve results, distinguishing it from siblings like get_audit_results.

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?

It explicitly explains the async workflow and the need to use get_audit_results later. It does not explicitly mention when not to use it versus search_query_audits or search_system_audits, but the context of 'sidecar query audits' provides some differentiation.

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/altrsoftware/altr-mcp-server'

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