Skip to main content
Glama
Sign In

WORKMINE

by io.github.Tamerlan0606
OverviewDiscussionsAdmin

workmine_payment_instructions

Return x402 payment and endpoint instructions for a selected WORKMINE tool without executing the paid call. Pass a tool slug returned by find_workmine_tool or workmine_catalog. The buyer then calls the endpoint, reads its HTTP 402 challenge, signs the exact Base USDC payment and retries.

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": {
      "tool": "<tool>"
    },
    "name": "workmine_payment_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesExact WORKMINE product slug returned by find_workmine_tool or workmine_catalog, for example x402_launch_kit, repair_json, or pdf_extract.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tool / description
      Added value: +"Exact WORKMINE product slug returned by find_workmine_tool or workmine_catalog, for example x402_launch_kit, repair_json, or pdf_extract."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description carries the full load and does well: it discloses the key non-obvious trait that no paid call is executed, and describes the payment round-trip (HTTP 402 challenge, Base USDC signing, retry). It omits auth/permission requirements and whether a signature is needed on this call itself.

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?

Three tight sentences, front-loaded with the core purpose and no padding; the non-execution caveat is placed early where it matters most.

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

Completeness5/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-value detail is not the description's burden. Combined with the schema and the described workflow, an agent has everything needed to call it correctly.

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 description coverage is 100% and the single parameter is already documented with examples, so the schema does the heavy lifting. The description restates the slug's origin rather than adding new syntax or format meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Return x402 payment and endpoint instructions for a selected WORKMINE tool') plus the crucial scope qualifier 'without executing the paid call'. An agent can distinguish this from sibling offer/ping tools without inspecting any schema.

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?

Explains the input's provenance ('Pass a tool slug returned by find_workmine_tool or workmine_catalog') and outlines the downstream buyer flow (call endpoint, read HTTP 402, sign USDC payment, retry), which gives clear context for when this step fits. It stops short of explicitly stating when NOT to use it versus siblings like workmine_paid_ping.

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

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

Resources