Spraay x402 MCP Server

spraay_payroll_estimate

Estimate gas and fees for a payroll batch before executing. Returns estimated gas in wei and USD for a cost of $0.002 USDC.

Instructions

Estimate gas and fees for a payroll batch before executing. Returns estimated gas in wei and USD. Costs $0.002 USDC.

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": {
      "employeeCount": "<employeeCount>"
    },
    "name": "spraay_payroll_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`token`	No	Payment token symbol (default: 'USDC')
`employeeCount`	Yes	Number of employees to pay (1-200)

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 indicate it's not read-only nor destructive, and the description adds that it costs $0.002 USDC, providing useful cost transparency. It does not detail other potential side effects, but the estimation nature is clear.

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 efficient sentences: the first states the core action, the second adds return format and cost. No unnecessary 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 the presence of an output schema, the description adequately covers the key aspects (action, return, cost). It could mention prerequisites or limit warnings but is sufficient for a simple estimation tool.

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 each parameter having a description. The description adds no additional parameter-specific meaning beyond the schema, but it does provide output context (gas in wei and USD) that indirectly helps.

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?

The description clearly states the tool's action ('Estimate gas and fees') and the resource ('payroll batch before executing'). It specifies the return values (gas in wei and USD) and cost, distinguishing it from related tools like spraay_payroll_execute.

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?

The description implicitly guides usage by stating 'before executing', indicating it's a pre-execution step. However, it does not explicitly list when not to use it or compare it to alternatives like spraay_batch_estimate.

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

Deploy Server