Skip to main content
Glama
Sign In
PayQL

PayQL

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get query price

get_payment_info

Retrieve USDC price, asset, payTo, and network for a subgraph query to estimate cost or set up payment without paying.

Instructions

Preflight a subgraph: return the USDC price, asset, payTo and network from the x402 402 challenge WITHOUT paying. Use to estimate cost or to drive a harness-side payment.

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": {
      "subgraph_id": "<subgraph_id>"
    },
    "name": "get_payment_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
subgraph_idYesSubgraph ID
queryNoGraphQL query to price (defaults to a minimal _meta probe)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It explicitly states key behavioral traits: preflight action without payment ('WITHOUT paying'). No contradictions, but could mention side effects or error handling.

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?

Description is a single, well-structured sentence. It front-loads the action and lists return fields efficiently with no wasted words.

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?

Given no output schema, the description lists return fields (USDC price, asset, payTo, network). It covers the primary behavior and inputs but could describe output structure or error scenarios more fully.

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 description coverage is 100% (both parameters have descriptions), so baseline is 3. The tool description does not add extra parameter semantics beyond the schema.

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?

Description clearly states the tool's purpose: 'Preflight a subgraph' to 'return the USDC price, asset, payTo and network' without payment. It uses specific verbs and specifies the resource, differentiating it from sibling tools like query_subgraph and search_subgraphs.

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?

Description provides clear usage context: 'Use to estimate cost or to drive a harness-side payment.' It implies when to use but does not explicitly state when not to use or compare with alternative tools.

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

Deploy Server

Other Tools