Skip to main content
Glama
Sign In

WORKMINE

by io.github.Tamerlan0606
OverviewDiscussionsAdmin

workmine_launch_kit_offer

Quote the premium WORKMINE x402 Launch Kit without charging anything. Use this when an API developer or autonomous agent wants to monetize an HTTP service with x402 on Base. Returns the exact $19 USDC product URL, required request fields, deliverables and payment flow. This MCP call is free and read-only; payment occurs only if the buyer later calls the returned HTTP endpoint and signs its x402 challenge.

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_launch_kit_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states the call is free and read-only and explains that payment happens only if the buyer later calls the returned HTTP endpoint and signs its x402 challenge. It doesn't cover idempotency or rate limits, but for a static offer tool that is a minor gap.

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 tight sentences, front-loaded with what the tool does before the usage condition and the payment caveat. Every sentence carries information, though the return-value sentence is slightly redundant given an output schema exists.

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?

For a zero-parameter, read-only offer tool with a declared output schema, the description supplies everything an agent needs: what it returns, that it is free, and where payment actually occurs. Nothing required for correct invocation is missing.

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 and the description does not invent any, so there is no parameter semantics to convey. Baseline for a 0-param tool is 4.

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?

The description names a specific verb and resource ('Quote the premium WORKMINE x402 Launch Kit') and characterizes the scope ('without charging anything'), which an agent can distinguish from the paid siblings. It stops short of explicitly comparing itself to the other workmine_* tools, but the free/read-only framing implicitly separates it from the paid ones.

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?

It gives a clear triggering condition: 'Use this when an API developer or autonomous agent wants to monetize an HTTP service with x402 on Base.' That is a concrete when-to-use statement, though no alternative tool is named for the case where the agent wants the paid product, so routing guidance is context-driven rather than explicit.

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