Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

Read a record's change history

heliyos_records_events
Read-onlyIdempotent

Retrieve a record's audit trail to see who changed what and when, with filters for operation, event type, date range, and text; use detailed mode for changed field paths.

Instructions

Returns the audit trail of one record: who changed what and when (people and workers), newest first, each with a one-line change summary. Filter by operation type, event type, date range or text. "detailed" adds the paths of the changed fields. Use heliyos_records_timeline instead for a narrative of the relationship. Returns structuredContent {events:[{id, at, operation_type, actor, change_summary}], next_cursor}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "record_id": "<record_id>"
    },
    "name": "heliyos_records_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEvents per page, 1 to 100. Default 20.
sinceNosince as an ISO 8601 date (2026-03-01) or date-time (2026-03-01T09:00:00Z).
untilNoOnly events at or before this date; a date alone includes that whole day (UTC).
cursorNonext_cursor from the previous page, with the same limit. Omit for the first page.
searchNoPlain words matched against the change summaries. Symbols such as + ( ) [ ] * ? can cause an error.
record_idYesrecord_id: a 24-character hex id.
event_typesNoOnly these event types: AUDIT (field changes), INTERACTION (emails, meetings), ENRICHMENT.
operation_typesNoOnly these operations: CREATE, UPDATE, DELETE.
response_formatNo"concise" (default) returns one line per change; "detailed" returns the changed field paths too.concise

Output Schema

NameRequiredDescriptionDefault
eventsYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavior beyond that: sort order (newest first), per-event shape (one-line change summary, actor can be a person or a worker), and that response_format='detailed' enlarges each entry with changed field paths. It does not discuss rate limits or maximum result depth, which is the remaining gap.

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?

Front-loaded and dense: core behavior first, then filtering, then the mode flag, then the sibling routing. The closing return-shape sentence is largely redundant given a full output schema exists, which is the one sentence that does not fully earn its place.

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?

For a 9-parameter read tool with annotations and an output schema, it covers intent, ordering, filtering, pagination via next_cursor and mode behavior. Nothing needed to call it correctly is missing, though it repeats the structuredContent shape that the output schema already defines.

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 description coverage is 100%, so the schema already documents limit, cursor, since/until, search, event_types, operation_types and response_format. The description only restates the available filter axes and the 'detailed' behavior, which the response_format schema description already says. Baseline 3 is appropriate because the schema carries the semantic load.

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?

States a specific verb and resource ('returns the audit trail of one record') and immediately scopes the payoff: who changed what, when, newest first, with one-line summaries. It also names the sibling it is not (heliyos_records_timeline) so an agent can separate event history from a narrative timeline without opening either schema.

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?

Explicitly routes the agent away from this tool when it wants a narrative of the relationship, naming heliyos_records_timeline as the alternative. It gives no guidance on the other close neighbors (heliyos_records_get for current field values, heliyos_tasks_events for task history), so the exclusion set is only partially drawn.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools