viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

metering__list_events

Retrieve paginated usage events filtered by meter, outcome, date range, and other criteria. Exclude test events unless requested.

Instructions

[metering — usage metering + SLA accounting (x402 meter)] Read usage events (paginated, read-only). Filter by meter, provider, consumer_class (internal|external|unknown), channel, outcome (ok|error), and ISO date range [since, until). Test-flagged events are excluded unless include_test=true. Returns events + next_cursor.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`since`	No
`until`	No
`cursor`	No
`channel`	No
`outcome`	No
`meter_id`	No
`provider`	No
`include_test`	No
`consumer_class`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.12Jul 28, 2026
Removedv0.1.11Jul 18, 2026
Changed36 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / channel / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / channel / default
```
Removed value: -null
```
- removedInput schema / properties / channel / title
```
Removed value: -"Channel"
```
- addedInput schema / properties / channel / type
```
Added value: +"string"
```
- removedInput schema / properties / consumer_class / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / consumer_class / default
```
Removed value: -null
```
- removedInput schema / properties / consumer_class / title
```
Removed value: -"Consumer Class"
```
- addedInput schema / properties / consumer_class / type
```
Added value: +"string"
```
- removedInput schema / properties / cursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / cursor / default
```
Removed value: -null
```
- removedInput schema / properties / cursor / title
```
Removed value: -"Cursor"
```
- addedInput schema / properties / cursor / type
```
Added value: +"string"
```
- removedInput schema / properties / include_test / title
```
Removed value: -"Include Test"
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / meter_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / meter_id / default
```
Removed value: -null
```
- removedInput schema / properties / meter_id / title
```
Removed value: -"Meter Id"
```
- addedInput schema / properties / meter_id / type
```
Added value: +"string"
```
- removedInput schema / properties / outcome / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / outcome / default
```
Removed value: -null
```
- removedInput schema / properties / outcome / title
```
Removed value: -"Outcome"
```
- addedInput schema / properties / outcome / type
```
Added value: +"string"
```
- removedInput schema / properties / provider / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / provider / default
```
Removed value: -null
```
- removedInput schema / properties / provider / title
```
Removed value: -"Provider"
```
- addedInput schema / properties / provider / type
```
Added value: +"string"
```
- removedInput schema / properties / since / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / since / default
```
Removed value: -null
```
- removedInput schema / properties / since / title
```
Removed value: -"Since"
```
- addedInput schema / properties / since / type
```
Added value: +"string"
```
- removedInput schema / properties / until / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / until / default
```
Removed value: -null
```
- removedInput schema / properties / until / title
```
Removed value: -"Until"
```
- addedInput schema / properties / until / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"list_eventsArguments"
```
Addedv0.1.8Jul 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses read-only nature, pagination via next_cursor, and test-event exclusion. However, it lacks details on rate limits, authentication, or error behavior.

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?

The description is a single sentence with front-loaded key information ('Read usage events (paginated, read-only)') followed by a list of filters. It is concise and clear, though slightly dense.

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 10 parameters, no output schema, and no annotations, the description covers the main purpose and filters but lacks details on return format, pagination mechanics, and parameter constraints. It is adequate but not fully complete.

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 0%, so the description must compensate. It lists filters and hints at enum values (e.g., consumer_class: internal|external|unknown; outcome: ok|error), but does not provide full value sets or format details for parameters like since/until.

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?

The description clearly states it reads usage events, is paginated, and read-only. It lists filters, making the purpose specific. However, it does not explicitly differentiate from sibling tools like metering__usage_summary or metering__usage_timeseries.

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 description enumerates filters and mentions test-flagged event exclusion, providing usage context. It does not give explicit when-to-use or alternatives, leaving some ambiguity.

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

Deploy Server

metering__list_events

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools