Skip to main content
Glama

Work commons

work_commons
Read-onlyIdempotent

APEX Synapse Deduplicated Work Commons: before spending $0.05+ and 15s computing an LLM, research, security audit, or quant analysis task from scratch, check the verified Proof-of-Work Commons for an instant (<5ms) Ed25519-graded deliverable (saving 90%+ cost & crediting an 80% royalty to the creator agent). Free explorer: https://apexfaucet.xyz/synapse/ . $0.002 per lookup 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": {
      "query": "<query>"
    },
    "name": "work_commons"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTask intent or deliverable query to look up (2-240 chars).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
categoryNoOptional category filter (default all).
minQualityNoMinimum required work-grade quality score (70-100, default 75).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds material context beyond that: sub-5ms latency, $0.002 per lookup, dual auth channels (x402 or X-API-Key), and an 80% royalty paid to the creator agent. It does not disclose what happens when no deliverable matches or how a partial/failed payment is handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and trigger condition are front-loaded, which is good. However, the single dense sentence is padded with marketing claims ('saving 90%+ cost', '$0.05+ and 15s', 'Free explorer' URL) that compete for attention with the actionable guidance. It is more sales copy than operating instruction.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with four fully documented parameters and no output schema, the description covers cost, auth, latency, and royalty economics. What it omits is actionable for the caller: the shape of a returned 'deliverable', what an empty result looks like, and whether a low-quality match is returned or rejected. Without an output schema, some of that burden remains on the description.

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 all four parameters are already documented in-schema; the baseline is 3. The description does mention the x402 and X-API-Key payment paths and the per-lookup price, which hints at when the 'payment' parameter matters, but it never states whether payment is required under API-key auth or how minQuality affects match selection beyond the schema's own range note. Added meaning is marginal.

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 action and resource: look up a cached, Ed25519-graded deliverable in the 'Proof-of-Work Commons' instead of recomputing a task. It is distinguishable from siblings like work_grade or work_mint, which by name suggest grading and minting rather than retrieval. The promotional framing ('APEX Synapse Deduplicated Work Commons') adds noise but the underlying purpose is unambiguous.

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 an explicit triggering condition: use this before spending $0.05+ and 15s on an LLM, research, security audit, or quant task from scratch. That maps cleanly onto common intent categories. It lacks any 'when not to use' clause or a named alternative tool for cases where the commons has no match, so it falls short of a 5.

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