Skip to main content
Glama

Archlooks.com - Interior design and architecture gallery

Access project page (x402 paid)

access_project

x402-gated project page access, $0.01. Call without payment to get the offer (accepts: Base USDC via EIP-3009 gasless, or legacy on-chain USDC/USDT/PYUSD on Solana/Tron/EVM). Then retry with payment.payload (base64 PaymentPayload) or payment.tx_hash + payment.network. Returns access_token + canonical URL.

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": {
      "project_id": "<project_id>"
    },
    "name": "access_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoPayment proof from the offer
project_idYesNumeric project id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds substantial context beyond the single readOnlyHint=false annotation: the $0.01 cost, the x402 offer/retry handshake, accepted payment rails (Base USDC via EIP-3009 gasless vs legacy on-chain on Solana/Tron/EVM), and the return payload. Not covered: whether a failed access still charges, or any rate/expiry behavior for the access_token.

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?

Three tight sentences, front-loaded with the gate and price, then the call sequence. Dense with domain jargon (x402, EIP-3009, PaymentPayload) but every clause carries operational information; no filler.

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 paid, two-phase call with a nested payment object and no output schema, the description covers the flow, the payment alternatives, and what is returned (access_token + canonical URL). A note on payment failure/refund semantics would make it fully complete.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning the schema cannot: the conditional nature of `payment` (omit it first to get an offer) and the mutually alternative forms within it (`payload` vs `tx_hash` + `network`). That clarifies how to fill the nested object rather than just what its keys are.

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 ('project page access') plus the gating mechanism and price, so the agent knows exactly what the call yields. It doesn't explicitly contrast itself with siblings get_project_card or search_projects, but the resource scope is distinct enough to infer.

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?

Gives an explicit two-step protocol: call without `payment` to obtain the offer, then retry with `payment.payload` or `payment.tx_hash` + `payment.network`. This is concrete invocation guidance. It lacks guidance on when to prefer this over the sibling tools, which keeps it from a 5.

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.

Resources