WORKMINE

workmine_paid_ping_offer

Free quote for WORKMINE Paid Ping, the minimum-cost $0.001 USDC x402 purchase. Use this when an autonomous agent wants to verify that it can complete an x402 payment before buying a larger tool. This MCP call is free and does not charge anything.

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_paid_ping_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

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses cost behavior ('This MCP call is free and does not charge anything'), which is the key concern for a paid-ping probe, but it says nothing about rate limits, auth prerequisites, or side effects of the probe itself.

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?

Three short sentences, front-loaded with the core identity before the usage condition. Slight redundancy in stating 'free' twice ('Free quote' and 'This MCP call is free'), costing it a point.

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?

An output schema exists, so return values need not be explained. The description covers identity, purpose, and cost, which is adequate for a zero-parameter probe tool, though it could say more about what the quote confirms.

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. There is nothing for the description to clarify beyond the schema, which is empty by design.

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?

States a specific resource (a free quote for WORKMINE Paid Ping) and quantifies the underlying purchase as the minimum-cost $0.001 USDC x402 transaction. This distinguishes it from the sibling workmine_paid_ping, whose name implies the actual paid call, though the differentiation is achieved indirectly rather than by naming it.

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?

Gives clear triggering context: 'Use this when an autonomous agent wants to verify that it can complete an x402 payment before buying a larger tool.' This is an explicit when-to-use with a stated purpose, but it names no explicit alternative or when-not condition.

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.