Skip to main content
Glama
Sign In

akari-x402

by io.github.edvyno
OverviewDiscussionsAdmin

akari_integrity_watch

Integrity Watch — 30 days of daily re-probing for ONE x402 seller host. We re-run the same buyer-path audit every day and alert on drift: grade changes, new payment-breaking defects, or a paywall that went dark. You get a secret watch page (HTML + JSON) and a live badge URL your README can embed. Sold to sellers who already have a live 402 and cannot see it break.

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": "akari_integrity_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well by disclosing daily re-probing, drift alert categories, the secret watch page, and the badge URL. It still omits authentication requirements, alert delivery details, and what happens after the 30-day period.

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 appropriately sized and front-loaded: it starts with the service definition, then explains drift monitoring, deliverables, and target user. Every sentence contributes useful information with no wasted wording.

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?

It covers the service behavior and outputs reasonably well, especially given no output schema. But for a zero-parameter monitoring tool, the missing explanation of how the seller host is identified is a critical gap, along with unstated auth and alert-delivery requirements.

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?

The input schema has zero parameters, so the baseline would normally be 4. However, the description introduces a required conceptual target — ONE x402 seller host — without explaining how that host is specified, leaving invocation ambiguous.

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 states a specific service: 30 days of daily re-probing for ONE x402 seller host, with drift alerts and deliverables. It clearly distinguishes single-host watch from the fleet-oriented sibling by emphasizing "ONE" host.

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?

It gives a clear intended context: sellers who already have a live 402 and cannot see it break. It also scopes the tool to one host, but it does not explicitly name the fleet alternative or state when not to use this tool.

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

All akari-x402 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