Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

update_report_definition

Update an audit report definition by replacing its entire configuration. Provide the definition ID, name, and integration type, along with optional settings like schedule and filters.

Instructions

Update an existing audit report definition (full replacement).

Replaces the definition's configuration entirely. All fields that should be preserved must be included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
definition_idYesID of the definition to update.
nameYesUnique display name for the definition.
integration_typeYesData source type. Values: "oltp", "snowflake".
descriptionNoOptional human-readable description.
lookback_daysNoNumber of complete calendar days to include in each report window (excludes the trigger day).
timezoneNoIANA timezone for the report window (e.g. "America/New_York").
schedule_cronNo6-field cron expression controlling when the report runs automatically. Format: "minute hour day-of-month month day-of-week year" Use ? in day-of-month OR day-of-week (not both) when the other field is specified. Use * for "every". Days: SUN MON TUE WED THU FRI SAT Months: JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Common examples — convert natural language like: "every day at 12 PM" → "0 12 * * ? *" "every day at 9 AM" → "0 9 * * ? *" "every Monday at 9 AM" → "0 9 ? * MON *" "every weekday at 8:30 AM" → "30 8 ? * MON-FRI *" "every Sunday at 6 PM" → "0 18 ? * SUN *" "first day of month midnight" → "0 0 1 * ? *" "every hour" → "0 * * * ? *"
schedule_enabledNoWhether the schedule is active.
schedule_timezoneNoIANA timezone for schedule evaluation (e.g. "America/New_York"). All cron times are interpreted in this timezone.
deliveryNoDelivery configuration as a dict or JSON string. Shape: {"channels": [{"type": "email", "enabled": bool, "recipients": ["email@example.com"]}]}.
filtersNoFilter groups as a dict or JSON string. Shape: {"filter_groups": [{"filters": [{"field": "database_name", "pattern": {"match_type": "exact", "value": "mydb"}}]}]}. OLTP fields: database_name, table_name, schema_name, column_name, statement_type, consuming_user, event_source, event_name, repo_user, repo_host, repo_name, repo_type, application_name, client_host, connection_id, statement_text, policy_blocked, execution_success, row_count. Snowflake fields: username, current_role, ip_address, client, query_type, warehouse, warehouse_size.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Since no annotations are provided, the description must disclose behavioral traits. It states the replacement behavior, which is non-obvious from the schema alone. However, it omits other potential effects like validation or impacts on active reports.

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 consists of two succinct sentences. The first states the purpose, and the second clarifies the behavioral constraint. No unnecessary words are present.

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?

Given the complexity of 11 parameters and an output schema, the description is minimal but adequately highlights the key behavioral aspect (full replacement). It does not describe return values, but the output schema exists to cover that.

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?

The input schema has 100% description coverage and provides detailed parameter descriptions (including cron examples and JSON shape). The tool description adds no extra meaning beyond what the schema already conveys, justifying the baseline score.

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 tool updates an existing audit report definition and specifies that it is a full replacement. This effectively distinguishes it from sibling tools like create_report_definition.

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 notes that the operation is a full replacement and that all fields to be preserved must be included. This provides clear guidance, though it could be improved by mentioning cases where partial updates are not supported via this tool.

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