Skip to main content
Glama

agent-exec

Signed observation of a URL (paid, x402)

attest_create

PAID: attest a URL: we fetch it and sign what we saw (hash, status, headers, never the body), timestamped. A failed fetch is still an observation. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

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

Input Schema

NameRequiredDescriptionDefault
urlNoAn absolute http:// or https:// URL, at most 2048 UTF-8 bytes. The body is never returned to you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses what is actually signed (hash, status, headers, never the body), that a failed fetch still produces an observation, the exact cost ($0.0100 USDC), the accepted chains, and the payment metadata key. That is unusually rich disclosure of cost, error semantics, and data handling for a mutation/paid tool.

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?

Front-loaded with "PAID: attest a URL" and the core semantics come first, which is the right structure. Minor waste: the feedback-channel sentence ("Read daily; no individual reply") does nothing to help an agent select or invoke the tool, and the price is stated twice.

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

Completeness4/5

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

For a one-parameter paid tool with no output schema, the description covers what is produced, what is excluded, failure behavior, and the payment handshake. The remaining gap is the shape of the returned attestation itself (identifier, signature format, expiry), which an agent may need to reference the result.

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 100% and the single url parameter is already documented in-schema with length constraints. The description adds only one piece of meaning beyond the schema: the fetched body is never returned to the caller. Otherwise the baseline of 3 applies.

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?

"attest a URL: we fetch it and sign what we saw (hash, status, headers, never the body)" gives a specific verb (attest/sign) and precisely defines the produced artifact, which is far stronger than the title alone. It does not differentiate itself from plausible siblings like check_url or scrape_page, so an agent must infer when attestation beats a plain check.

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?

The two-step x402 flow is spelled out concretely: an unpaid call returns the price, then you retry with payment in _meta['x402/payment']. This is the critical procedural guidance an agent needs. What is missing is any when-to-use-this-vs-alternatives or when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.