Spraay x402 MCP Server

spraay_compute_estimate

Read-only

Plan your AI compute spending by estimating costs for text, image, video, and other jobs. Get a price breakdown per job without payment.

Instructions

Estimate compute cost before committing. Returns price breakdown per job. FREE — no x402 payment required.

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": {
      "jobs": "<jobs>"
    },
    "name": "spraay_compute_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`jobs`	Yes	Jobs to estimate pricing for

Output Schema

Name	Required	Description
`ok`	Yes	True when the gateway call succeeded; false when it returned an error.
`data`	No	The gateway response payload on success. The exact shape depends on the tool (see the tool description and the JSON in the text content block).
`error`	No	Human-readable error message, present only when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.0Jun 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds 'FREE — no x402 payment required' and 'Returns price breakdown per job', which are useful behavioral traits beyond 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?

Two sentences, essential info front-loaded, no wasted words. Perfectly concise.

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?

Tool is simple with one parameter, schema covers everything, output schema exists. Description covers purpose, return value, and cost. Could be slightly more specific about the breakdown format, but output schema fills that gap.

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 coverage is 100% with descriptions for jobs, type, and model. The description repeats 'per job' but does not add additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 estimates compute cost and returns a price breakdown per job. It uses specific verb 'Estimate' and resource 'compute cost', and distinguishes itself from similar tools like spraay_compute_batch (execution) by noting 'before committing'.

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 implies use for upfront cost estimation and highlights it's free (no x402 payment). However, it does not explicitly exclude execution tools or mention when not to use it, but the context is clear for a simple estimate tool.

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

Deploy Server