Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

metering__close_period

Finalize open usage events into an immutable, exactly-once invoice for agent settlement. Requires meter ID.

Instructions

[metering — usage metering + SLA accounting (x402 meter)] Freeze all open events into an immutable invoice (exactly-once). The invoice amount is what agent-escrow-agent should settle.

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": {
      "meter_id": "<meter_id>"
    },
    "name": "metering__close_period"
  }
}

Input Schema

NameRequiredDescriptionDefault
meter_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.12
  2. Removedv0.1.11
  3. Changed2 schema fields changedv0.1.9
    • removedInput schema / properties / meter_id / title
      Removed value: -"Meter Id"
    • removedInput schema / title
      Removed value: -"close_periodArguments"
  4. Changed2 schema fields changed
    • addedInput schema / properties / meter_id / title
      Added value: +"Meter Id"
    • addedInput schema / title
      Added value: +"close_periodArguments"
  5. Changed2 schema fields changed
    • removedInput schema / properties / meter_id / title
      Removed value: -"Meter Id"
    • removedInput schema / title
      Removed value: -"close_periodArguments"
  6. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It mentions 'exactly-once' and 'immutable', which hint at idempotency and finality, but lacks details on reversibility, permissions, rate limits, or side effects on events. The description is too brief to provide adequate transparency.

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 is extremely concise, consisting of two sentences and a prefix. Every word adds value, and it is front-loaded with the tool's purpose. No unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that performs a critical action (closing a period, freezing events, creating an invoice), the description lacks information about return values, error conditions, prerequisites, or what happens to existing events. The complexity warrants more detail, especially without an output schema.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not explain the meter_id parameter. No additional meaning is provided beyond the schema's type and name. The description fails to compensate for the lack of parameter documentation.

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 that the tool freezes open events into an immutable invoice for settlement, using specific verbs like 'Freeze' and 'immutable invoice'. It implies a finalization action within the metering suite but does not explicitly differentiate from sibling tools like metering__usage_summary or metering__list_events.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies it is for closing a period, but there is no mention of prerequisites, when not to use it, or comparisons to other metering tools.

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