Skip to main content
Glama

l402_stats

Fetches payment and usage statistics from the configured L402 gateway for monitoring transaction activity and service usage.

Instructions

Fetch gateway payment and usage statistics from the configured L402 gateway.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "l402_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. "Fetch" implies a read-only operation and "configured L402 gateway" signals a configuration prerequisite, but it says nothing about whether the call is authenticated, how far back statistics go, or whether results are paginated or aggregated.

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?

A single twenty-word sentence with no filler, and the key concept (payment and usage statistics) is placed early. It is efficient, though its brevity contributes to the missing usage and behavior detail.

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?

The tool is simple — no parameters, no output schema — so minimal description is defensible, but with no output schema the description should still hint at what the statistics contain (payment volume, request counts, time window). As written, an agent knows what the tool fetches but not what it will receive.

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?

The tool takes zero parameters, so the baseline is 4. The phrase "configured L402 gateway" usefully explains why no gateway argument is needed — the target comes from configuration — which is the only semantic the agent needs here.

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 uses a specific verb ("Fetch") and names the resource precisely: gateway payment and usage statistics. It is distinguishable from siblings like l402_balance (account balance) and l402_inspect, though it does not explicitly contrast itself with them.

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?

There is no guidance on when to call this rather than l402_balance, l402_check, or l402_inspect, all of which could plausibly surface overlapping information. The only implicit context is that it requires a configured gateway, but no exclusions or selection criteria are stated.

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