Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

gateway_stats

Seller side: calls, revenue and recent activity for one of your gateway endpoints. Read-only. REQUIRES OPERATOR KEY.

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": {
      "endpoint_id": "<endpoint_id>"
    },
    "name": "gateway_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpoint_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Since no annotations are provided, the description must carry the full burden. It explicitly states the operation is 'Read-only' and, critically, highlights a necessary operational trait: 'REQUIRES OPERATOR KEY,' which is vital behavioral context.

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 definition is extremely concise and highly structured, front-loading the resource type and the critical security prerequisite immediately. It provides maximum information density for its length.

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

Completeness5/5

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

Given the tool is simple (one required parameter, no output schema), it is complete. It defines *what* it returns (stats), *how* to access it (operator key), and *what* the parameter refers to (one gateway endpoint).

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 coverage is 0%, but since there is only one required parameter ('endpoint_id') and its meaning is clear from the schema and context, the description doesn't have much to add semantically beyond stating the scope it applies to.

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 defines the resource ('gateway endpoints') and the specific data provided ('calls, revenue and recent activity'), distinguishing it as a 'stats' tool rather than a management tool like gateway_update.

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

Usage Guidelines4/5

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

While it doesn't explicitly compare itself to other list/read tools (like gateway_list or gateway_catalog), it clearly defines the scope (one specific endpoint) and sets a major prerequisite (REQUIRES OPERATOR KEY) which guides usage and access control.

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

All Lightning Wallet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources