AZPay Monetize — Sepolia Sandbox

Get quote

get_quote

Read-only

Use this when you already have a resource_id and need the list price, floor, volume tiers, and URL. Use negotiate_price to propose a different price. Required input: resource_id from search_resources. Returns the quote. Does not change the price or pay.

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": {
      "resource_id": "<resource_id>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description	Default
`resource_id`	Yes	Required. Resource id returned by search_resources.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026

removedInput schema / properties / id

Removed value: -{
-  "description": "Deprecated alias of resource_id.",
-  "maxLength": 120,
-  "type": "string"
-}

changedInput schema / properties / resource_id / description

Previous value: -"Resource id returned by search_resources."New value: +"Required. Resource id returned by search_resources."

addedInput schema / properties / resource_id / minLength
```
Added value: +1
```
addedInput schema / required
```
Added value: +[
+  "resource_id"
+]
```

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description reinforces it with "Does not change the price or pay." It also discloses the payload contents, which matters because there is no output schema—only missing pricing/currency semantics or staleness notes keep it from a 5.

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?

Four short sentences, front-loaded with the selection condition and zero filler. "Returns the quote" is mildly redundant with the field list in the first sentence, but it is a minor cost.

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?

For a single-parameter read tool with no output schema, the description covers trigger condition, alternative routing, returned fields, and non-mutation guarantees. Nothing an agent needs in order to call it correctly is missing.

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?

One parameter at 100% schema coverage, so the schema already documents resource_id fully; the description repeats the same provenance hint ("from search_resources"). Baseline 3 is appropriate—no syntax or format detail is added beyond the structured field.

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?

States a specific verb (get) and resource (quote), enumerates the returned data (list price, floor, volume tiers, URL), and names the sibling it is not (negotiate_price). An agent can distinguish it from search_resources and negotiate_price without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ("when you already have a resource_id") plus the alternative and the condition selecting it ("Use negotiate_price to propose a different price"). The closing sentence also rules out mutation and payment, covering the when-not case.

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

All AZPay Monetize — Sepolia Sandbox tools Inspect

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

Need Help?