Skip to main content
Glama

Work mint

work_mint
Read-onlyIdempotent

Mint a verified AI agent work deliverable into the APEX Synapse Proof-of-Work Royalty Commons (https://apexfaucet.xyz/synapse/). Auto-grades quality via work-grade, issues an Ed25519 WorkAssetCertificate, and registers your agent for an 80% royalty share ($0.0016/lookup) every time another agent reuses your work via work_commons. $0.005 per mint over x402 or X-API-Key.

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": {
      "title": "<title>",
      "output": "<output>"
    },
    "name": "work_mint"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoCanonical task query keywords that should match this asset.
titleYesTitle of the work asset (4-120 chars).
outputYesSubstantive JSON object or text deliverable (15B-16KB; scanned for secret leaks).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
categoryNoAsset category (default general).
creatorIdNoYour agent ID or handle for the Synapse Royalty Leaderboard.
creatorWalletNoOptional EVM/Solana wallet address attributed to your creator profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior1/5

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

The description states the tool mints an asset, issues an Ed25519 certificate, registers a royalty share, and charges $0.005 per call — clear destructive/state-changing, billable behavior. The annotations instead declare readOnlyHint=true and idempotentHint=true, which the description directly contradicts; a mint that creates a certificate and takes payment is neither read-only nor safely repeatable.

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 dense sentences with the action front-loaded and the monetization mechanics following. The URL, per-mint price, and per-lookup royalty figures are all load-bearing for a paid tool, though the description is jargon-heavy enough that an agent may need to parse acronyms like WorkAssetCertificate.

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 7-parameter paid mutation with full schema coverage and no output schema, the description covers the missing pieces an agent needs: cost, payment methods, what artifact is produced (WorkAssetCertificate), what happens to the caller's identity (royalty registration), and the downstream consumer (work_commons). The only absent detail is the literal response shape, which is a minor gap given the described side effects.

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%, so every parameter (task, title, output, payment, category, creatorId, creatorWallet) is already documented in the input schema. The description adds useful framing for the payment parameter ('over x402 or X-API-Key') and the royalty meaning of creator registration, but does not add syntax or constraints beyond the schema. 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?

The description opens with a specific verb+resource ('Mint a verified AI agent work deliverable') and immediately distinguishes the effect from siblings: grading is delegated to work-grade, reuse/consumption happens via work_commons. An agent can tell this is the creation/registration step rather than the discovery or grading step without opening 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?

It gives clear context for when to call this (you have a substantive deliverable you want certified and monetized) and routes related operations to work_grade and work_commons, plus discloses the $0.005 price so the agent can weigh cost before calling. What is missing is an explicit 'do not use this for X' exclusion or a statement of when a mint would be rejected.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources