agent-guild

Agent Guild paid operations (free to read)

guild_paid_operations

Read-onlyIdempotent

FREE. Returns every paid operation with its CURRENT price, exact callable entrypoint, x402 settlement resource, and the free alternative to each. It also returns literal buyer intents for semantic tool selection. No account, no key, no human — calling this costs nothing.

best_agent — "which agent should I hire for this capability?" signed_decision — "get a signed trust decision for an agent hire." payment_decision — "is this wallet safe to pay?" protected_payment_decision — "protect a high-value USDC payment." machine_envelope — privacy-preserving signed message/intent commitment: authenticated sender, recipient, exact payload digest, nonce, expiry and optional value terms. Verification is free; the Guild attests provenance, not message truth. deep_preflight — live verification of an endpoint before you trust it. evidence_bundle — an offline-verifiable signed endpoint observation with a salted commitment and Merkle inclusion proof against a signed checkpoint. Buy with guild_evidence_bundle through this same MCP connection; retain the result and verify with the standalone Python/Node verifier, or call guild_evidence_verify free. The issuer attests its own observation and timestamps, not independently proven truth or endpoint safety. HTTP: POST /evidence/bundle. watch_cycle — scheduled re-verification billed in sandbox account credits per executed cycle; requires a billing key.

One-off paid operations use x402 (USDC on Base mainnet): pay per call from the 402 challenge without an account or sales contact. Watch cycles use sandbox credits and do not accept x402 payments.

Prices are deliberately NOT written into this description — they move, and a stale number is worse than none. Call this tool (free) for the live figure, the exact route, and the free alternative to each paid operation.

Example: guild_paid_operations()

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	No
`operations`	No
`authentication`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

addedOutput schema / properties / operations / items / properties / payment_mode

Added value: +{
+  "enum": [
+    "x402",
+    "credits_sandbox"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / operations / items / properties / settlement / description

Previous value: -"canonical resource the x402 challenge binds; an identifier, not a call"New value: +"canonical x402 settlement resource or internal sandbox billing identifier; not necessarily a callable route"

Changed1 schema field changedAug 13, 2026

addedOutput schema / properties / operations / items / properties / buyer_intents

Added value: +{
+  "description": "literal jobs autonomous buyers can match semantically to this operation",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 2,
+  "type": "array"
+}

Changed1 schema field changedAug 1, 2026

addedOutput schema / properties

Added value: +{
+  "authentication": {
+    "type": "object"
+  },
+  "operations": {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "directly_callable": {
+          "type": "boolean"
+        },
+        "entrypoint": {
+          "additionalProperties": true,
+          "description": "how to CALL it: method, path, where parameters go, auth",
+          "type": "object"
+        },
+        "free_alternative": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        },
+        "payment": {
+          "type": "string"
+        },
+        "price_credits": {
+          "type": "integer"
+        },
+        "price_usd": {
+          "description": "current, live",
+          "type": "string"
+        },
+        "settlement": {
+          "additionalProperties": true,
+          "description": "canonical resource the x402 challenge binds; an identifier, not a call",
+          "type": "object"
+        },
+        "what_you_get": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "source": {
+    "type": "string"
+  }
+}

AddedAug 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context: it is FREE, costs nothing, and explains why prices are not hardcoded ('they move, and a stale number is worse than none'). It also clarifies that verification for some operations is free while others require billing keys. This goes beyond the annotations.

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

Conciseness2/5

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

The description is extremely verbose, listing seven separate paid operations with individual descriptions. While this is informative, it is not concise. The core purpose could be captured in two sentences: 'Returns a catalog of all paid operations with current prices, endpoints, and free alternatives. Prices are dynamic; call to get live data.' Instead, the description becomes a mini-manual, which is more than needed for tool selection and invocation.

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?

Given that the tool has an output schema (not shown but indicated), the description does not need to explain the return format. It covers the key aspects: what is returned, that it's free, that prices are dynamic, and provides an example call. It also mentions payment methods (x402 vs sandbox credits) and the availability of free alternatives, making it complete for a zero-parameter read-only tool.

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 has zero parameters, so the input schema is empty. The baseline for 0 parameters is 4, and the description does not need to explain any parameter semantics. It adds no parameter info, but none is required. The description's extensive detail about what the tool returns compensates for the lack of parameter guidance.

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 clearly states a specific verb and resource: it returns every paid operation with its current price, exact callable entrypoint, x402 settlement resource, and free alternative. It explicitly says it's free to read and provides an example call. This unambiguously distinguishes it from sibling tools like guild_index or guild_capabilities, which are also catalogs but not specifically about paid operations.

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?

The description provides explicit when-to-use guidance: 'Call this tool (free) for the live figure, the exact route, and the free alternative to each paid operation.' It also states that no account, key, or human is needed, making it the go-to for anyone considering a paid operation. It doesn't explicitly say when not to use it, but given it's free and read-only, that omission is minor.

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

All agent-guild 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.