Skip to main content
Glama
Sign In
kwctl

kwctl

by KilaWattCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

x402_quote

Get the current price and Base USDC payment details for a GPU job without paying.

Instructions

Get the current price and Base USDC payment details for a GPU job without paying.

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

Input Schema

NameRequiredDescriptionDefault
gpu_typeNonvidia-h100
card_countNo
workload_typeNo
routing_policyNo
duration_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'Without paying' discloses one important trait (no charge is incurred) and 'current' hints at dynamic pricing, but nothing is said about whether a quote reserves capacity, whether it expires, what permissions are needed, or the response shape.

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?

A single front-loaded sentence with zero filler that states the purpose, the key non-charging behavior, and the payment context in one pass.

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

Completeness2/5

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

For a 5-parameter tool with no annotations and no output schema, the description omits the parameter meanings and the return contents that an agent would need. It adequately conveys only the top-level purpose, leaving significant gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Five parameters exist with 0% schema description coverage and three enums whose meanings (routing_policy, workload_type, duration_seconds, gpu_type) are entirely unexplained. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap.

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 description names a specific verb ('Get'), resource ('current price and Base USDC payment details'), and scope ('for a GPU job'). The phrase 'without paying' implicitly contrasts it with x402_run_job, so an agent can roughly distinguish it from the paying sibling, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

'Without paying' implies this is a pre-payment preview step, so usage is inferable, but there is no explicit when-to-use statement, no direction to call this before x402_run_job, and no prerequisites or exclusions. The routing to alternatives is left to inference.

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