verify_chain
Verify the tamper-evident event hash chain for a meter.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| meter_id | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
agent-metering
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. The description is too brief—it does not indicate whether the operation is read-only, if it modifies state, or what side effects occur (e.g., updates a verification log).
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, front-loaded sentence that is efficient. However, given the lack of detail, it prioritizes brevity over completeness, which slightly reduces its value.
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?
Despite having an output schema, the description does not explain what the tool returns (e.g., a boolean success flag or detailed chain status). The tool is simple (one parameter) but still requires more context to be fully self-contained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no information about the 'meter_id' parameter beyond what the schema already provides (type and required status). The agent gets no additional context to correctly populate the parameter.
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?
The description clearly states the tool's action ('Verify') and resource ('tamper-evident event hash chain for a meter'). It distinguishes itself from sibling tools like list_events or usage_summary which serve different purposes.
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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage solely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct aspect of usage metering: creating meters, recording events, generating reports, flagging synthetic data, closing periods, and verifying chain integrity. No two tools have overlapping purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., close_period, create_meter, list_events). No deviations or mixed conventions.
Tool Count5/5
With 11 tools, the set is well-scoped for a metering server. It covers creation, recording, listing, reporting, admin flags, period closing, and chain verification without being unnecessarily large.
Completeness4/5
The core lifecycle is covered: create meter, record usage, list events, generate reports, close period. Missing are tools to update/delete meters or retrieve invoices, but these are minor gaps given the immutable design intent.