Skip to main content
Glama

Paid URL and price

how_to_pay
Read-onlyIdempotent

Get the exact URL to call for a paid answer, with its price, network and asset. Pass the endpoint key and the query parameters you plan to send; they go through the same free check the API runs before payment, so a query that would be refused or come back empty shows up here. This tool never calls the paid endpoint and never pays. Payment is x402: no account or API key, USDC on Base.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "how_to_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoQuery parameters you plan to send, as strings, e.g. {"city": "McAllen"}. list_endpoints gives each endpoint's parameters and valid values. Omit for a call with no parameters.
endpointYesEndpoint key from list_endpoints, e.g. snapshot or series-permits-weekly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / endpoint / enum
      Previous value: -[
      -  "snapshot",
      -  "projects",
      -  "companies",
      -  "nearby",
      -  "parcel",
      -  "cost-per-sqft",
      -  "materials",
      -  "series-permits-weekly",
      -  "series-permits-monthly",
      -  "series-cost-basket-weekly",
      -  "series-absorption",
      -  "series-labor-ranges",
      -  "series-calls",
      -  "issue",
      -  "bridge-wait",
      -  "bridge-hourly",
      -  "crossings",
      -  "peso",
      -  "diesel",
      -  "sales-tax",
      -  "new-outlets",
      -  "alcohol-sales",
      -  "home-health",
      -  "industry"
      -]New value: +[
      +  "snapshot",
      +  "projects",
      +  "companies",
      +  "nearby",
      +  "parcel",
      +  "cost-per-sqft",
      +  "materials",
      +  "series-permits-weekly",
      +  "series-permits-monthly",
      +  "series-cost-basket-weekly",
      +  "series-absorption",
      +  "series-labor-ranges",
      +  "series-calls",
      +  "issue",
      +  "bridge-wait",
      +  "bridge-hourly",
      +  "crossings",
      +  "peso",
      +  "diesel",
      +  "sales-tax",
      +  "new-outlets",
      +  "alcohol-sales",
      +  "home-health",
      +  "industry",
      +  "ask"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / endpoint / enum
      Previous value: -[
      -  "snapshot",
      -  "projects",
      -  "companies",
      -  "nearby",
      -  "parcel",
      -  "cost-per-sqft",
      -  "materials",
      -  "series-permits-weekly",
      -  "series-permits-monthly",
      -  "series-cost-basket-weekly",
      -  "series-absorption",
      -  "series-labor-ranges",
      -  "series-calls",
      -  "issue"
      -]New value: +[
      +  "snapshot",
      +  "projects",
      +  "companies",
      +  "nearby",
      +  "parcel",
      +  "cost-per-sqft",
      +  "materials",
      +  "series-permits-weekly",
      +  "series-permits-monthly",
      +  "series-cost-basket-weekly",
      +  "series-absorption",
      +  "series-labor-ranges",
      +  "series-calls",
      +  "issue",
      +  "bridge-wait",
      +  "bridge-hourly",
      +  "crossings",
      +  "peso",
      +  "diesel",
      +  "sales-tax",
      +  "new-outlets",
      +  "alcohol-sales",
      +  "home-health",
      +  "industry"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare readOnly, idempotent, non-destructive, and closed-world. The description goes well beyond that by stating it never calls the paid endpoint and never pays, that queries which would be refused or come back empty surface here, and that payment uses x402 with no account/API key via USDC on Base. That is meaningful context an agent could not infer from the annotations.

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?

Three short sentences, front-loaded with the deliverable, then the mechanism, then the payment model. Every sentence carries distinct information with no repetition of schema or annotation content beyond what is necessary.

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 still tells the agent what comes back (URL, price, network, asset), what the tool does not do, and how payment works. For a two-parameter lookup tool this covers everything an agent needs to call it correctly.

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 baseline is 3, and the description adds real value by explaining that both the endpoint key and the submitted params are run through the pre-payment check, which tells the agent the params are actually validated here rather than just forwarded. It does not add format or syntax detail beyond the schema, hence not a 5.

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 first sentence names a specific verb and deliverable: get the exact URL to call for a paid answer, plus its price, network and asset. It clearly distinguishes the tool's role as a pre-payment lookup, though it never names its siblings (get_sample, get_free_series, list_endpoints) to contrast against.

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 clear operational context: pass the endpoint key and the query params you plan to send, and they run through the same free check the API performs before payment. It lacks an explicit statement of when to prefer get_sample or list_endpoints instead, but the 'before payment' framing makes the usage obvious.

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