Skip to main content
Glama

AvianSuite

by com.aviansuite
OverviewDiscussionsAdmin

List changes

list_changes
Read-only

Use to see what changed in a time window, optionally only one agent's changes or one entity's. Use it to review an agent's work, and before undo_changes to find the actor name and window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorNoOnly changes made by this actor (the agent credential name shown in results).
limitNoMost changes to return, newest first. Default 50.
sinceYesStart of the window: an RFC 3339 time, or a duration back from now such as 30m, 2h or 24h.
untilNoEnd of the window, RFC 3339. Defaults to now.
entity_idNoOnly changes to this entity.
workspaceNoOptional. The workspace to act on, as list_workspaces names it. Leave it out to use this connection's first workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
+  "description": "Optional. The workspace to act on, as list_workspaces names it. Leave it out to use this connection's first workspace.",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only a little beyond that: it implies the results carry actor names and a window, which helps the caller use the output before undo_changes. No return format, pagination, or ordering detail is offered (schema covers limit/order).

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?

Two sentences, no filler, and the primary action ('see what changed in a time window') is front-loaded before the filtering options and the undo_changes pointer.

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 6-parameter, read-only listing tool with full schema coverage and no output schema, the description covers purpose, usage context, and the downstream workflow with undo_changes. It could say a bit more about what a change record contains or how paging behaves, but nothing essential to a correct call is missing.

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 all six parameters (since, until, actor, entity_id, limit, workspace) are documented in the schema itself with formats such as RFC 3339 and duration shorthand. The description only restates the actor/entity filtering at a high level and adds no syntax or format meaning 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?

States a specific verb and resource ('see what changed') plus the scope ('in a time window') and the two optional narrowings (one agent, one entity). It also names the related sibling undo_changes, so an agent can place it without opening other schemas.

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 says when to reach for it: 'review an agent's work' and 'before undo_changes to find the actor name and window.' That is concrete context and links it to a workflow. It stops short of stating when not to use it or naming alternatives for pure entity inspection (e.g. get_entity).

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

All AvianSuite toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources