WORKMINE

workmine_readiness_audit_offer

Quote the WORKMINE x402 Readiness Audit without charging anything. Use this first for sellers who already have an x402 manifest and want a low-cost preflight check before marketplace registration. The audit costs $0.05 USDC on Base and checks identity, HTTPS resources, x402 v2 metadata, Base/USDC, payTo format, machine-readable discovery and origin consistency. This MCP call is free; payment occurs only when the buyer calls the returned HTTP endpoint.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses pricing ($0.05 USDC on Base), that the MCP call is free, and that payment occurs only when the buyer calls the returned HTTP endpoint. It does not state what checks the audit performs in detail, though it lists the subjects (identity, HTTPS, metadata, etc.).

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?

The information is front-loaded with the core guarantee (free quote) and then pricing and caveats. Some sentences are long but each earns its place.

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?

The description covers purpose, cost, scope, and the payment boundary. It is complete enough for a zero-parameter offer tool, though it could be more explicit about what the buyer receives in return.

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?

The tool takes zero parameters, so the baseline is 4. The description does not add parameter semantics beyond that, but none are needed.

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 names the specific action (quote an x402 Readiness Audit offer without charge) and scopes it to sellers who already have an x402 manifest. It distinguishes itself from paid siblings by stating it is a no-charge quote.

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?

Explicitly says to use this first for sellers with an x402 manifest wanting a preflight check before marketplace registration. It also scopes when payment occurs, clearly separating the free quote from the paid execution.

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

All WORKMINE 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.