Skip to main content
Glama
Sign In

KeeSpecs

by xyz.keespecs
OverviewDiscussionsAdmin

quote_anchors

Read-only

Newest movement of Keeta's anchors in one activity page, and the median block fee. Returns the x402 payment quote for this read (price, network, asset, pay-to, and the exact URL). It does not return data. To buy, GET the returned URL over HTTP and pay with x402; check get_x402_health first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial context beyond annotations: it discloses that the tool returns only a payment quote (price, network, asset, pay-to, URL), not data, and explains the HTTP/x402 payment workflow and the prerequisite health check.

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 three sentences with useful information in each. It is mostly front-loaded, though the first sentence describes the underlying data being quoted before clarifying that the tool returns only the quote.

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?

With no output schema, the description must explain the return value, and it does: it names the quote fields and clarifies that data is not returned. It also supplies the necessary payment workflow for a complex x402 operation.

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 has zero parameters, so parameter semantics are inherently minimal. The description correctly does not invent parameters and the schema is empty with full coverage.

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 clearly states that the tool returns an x402 payment quote for reading anchor-movement data and explicitly says it does not return the data itself. It is distinguishable from data-returning siblings like get_activity, though it does not name them directly.

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 concrete next step: GET the returned URL over HTTP and pay with x402, and advises checking get_x402_health first. It does not explicitly name the alternative data tool to use when no quote is needed, but the 'does not return data' caveat implies the boundary.

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

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