Skip to main content
Glama
mizcausevic-dev

mcp-kinetic-gain

by mizcausevic-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

audit_events_query

GET recent governance events from a running audit-stream-py instance (AUDIT_STREAM_URL and AUDIT_STREAM_TOKEN), optionally filtered by kind or source. The service does not combine both filters.

Instructions

GET recent governance events from a running audit-stream-py instance (AUDIT_STREAM_URL and AUDIT_STREAM_TOKEN), optionally filtered by kind or source. The service does not combine both filters. Returns the events array plus a count field; recorded source labels are caller-asserted. Returns a structured error when unconfigured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoFilter by event kind (exact match). Omit to get all kinds.
limitNoCap the number of events requested to at most 1000. Responses are separately capped at 1 MB.
sourceNoFilter by source (exact match). Omit to get all sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / kind / maxLength
      Added value: +128
    • addedInput schema / properties / kind / minLength
      Added value: +1
    • addedInput schema / properties / kind / pattern
      Added value: +"^[a-z][a-z0-9_]*$"
    • changedInput schema / properties / limit / description
      Previous value: -"Cap the number of events returned. Defaults to the server's own cap."New value: +"Cap the number of events requested to at most 1000. Responses are separately capped at 1 MB."
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • removedInput schema / properties / since_id
      Removed value: -{
-  "description": "Return only events with event_id > since_id. Use for incremental tailing without re-fetching the whole chain.",
-  "minimum": 0,
-  "type": "integer"
-}
    • addedInput schema / properties / source / maxLength
      Added value: +128
    • addedInput schema / properties / source / minLength
      Added value: +1
    • addedInput schema / properties / source / pattern
      Added value: +"^[A-Za-z0-9][A-Za-z0-9_.:-]*$"
  2. First observedv0.9.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the required environment configuration (AUDIT_STREAM_URL, AUDIT_STREAM_TOKEN), the mutual-exclusivity of the filters, the return shape (events array plus count), the caveat that source labels are caller-asserted, and the structured-error behavior when unconfigured.

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?

Three front-loaded sentences with no filler: the core action comes first, then the filter constraint and return shape, then the error/config caveat. Every sentence carries information an agent needs.

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 3-optional-parameter read tool with no output schema and no annotations, the description covers config prerequisites, filtering semantics, return structure, and error handling. It stops short of naming sibling alternatives or pagination behavior, but nothing critical to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter and a baseline of 3 would be defensible. The description adds real value beyond the schema by stating that kind and source filters cannot be combined, a parameter-interaction rule the schema does not encode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (GET) and resource (recent governance events from a running audit-stream-py instance), so the agent knows it is a read/query operation. It implicitly distinguishes itself from siblings like audit_event_emit, audit_event_compose and audit_event_inspect, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'optionally filtered by kind or source' implies how to call it, and 'The service does not combine both filters' hints at the constraint. However, there is no explicit statement of when to reach for this tool versus audit_event_inspect or the chain-verify siblings, so guidance is only implied.

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