Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

agentkit__uptime

Check x402 seller uptime and price. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: POST https://api.firstmention.uk/s/agentkit/uptime

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / urls
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / required
      Removed value: -[
-  "urls"
-]
  2. Added

TDQS

C2.9/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 burden. It does disclose genuinely useful behavior: cost ($0.01 USDC on Base eip155:8453), the x402 payment payload location (params._meta['x402/payment']), and the HTTP transport. What it omits is equally important: what constitutes 'uptime', what happens when the seller is down, and whether the call fails or returns a status.

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 purpose is front-loaded in the first clause, and the pricing/payment/endpoint facts are packed tersely without filler. The second sentence is dense but every element earns its place as invocation-critical metadata.

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 paid, single-parameter probe tool with no annotations and no output schema, the definition should say what the parameter is and roughly what comes back (uptime status, observed price, latency). Neither is present, so an agent can form the call but cannot predict or interpret the result.

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?

One parameter at 0% schema description coverage, and the description never explains it. Whether 'url' is the seller endpoint to probe, a base URL, or something else is left entirely to inference, despite this being the only input the caller must reason about.

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?

States a specific verb and resource: 'Check x402 seller uptime and price.' An agent knows this probes a seller endpoint for availability and pricing. It does not, however, differentiate itself from the many overlapping siblings such as x402check__check, x402_preflight__check, or x402index__trust, so the scope distinction must be inferred.

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 use this versus alternatives, no statement of prerequisites beyond payment, and no mention that the single 'url' parameter identifies the seller being probed. The payment/precondition detail is useful but does not substitute for use-case routing.

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

All automaton 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