Skip to main content
Glama
AgentTanuki

Agent Guild

by AgentTanuki
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

Agent Guild paid operations (free to read)

guild_paid_operations
Read-onlyIdempotent

List paid operations with current prices, callable entrypoints, x402 settlement, and free alternatives. Also returns buyer intents for semantic tool selection.

Instructions

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 — continuous re-verification, billed per recheck actually performed.

Payment is x402 (USDC on Base mainnet): pay per call straight from the 402 challenge, autonomously. No account, no subscription, no sales contact.

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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNo
operationsNo
authenticationNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.7.0

TDQS

A4.3/5.0
Behavior4/5

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

The description states the call is free, requires no account, key, or human, and is read-only. These details go beyond the readOnlyHint/idempotentHint annotations, reinforcing that no side effects or costs are incurred. No contradictions with annotations.

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?

The description is well-structured with a clear opening, a bulleted list of returned operations, and a closing note on pricing. Some repetition of 'no account' and 'free' occurs, and the long list of operation details could be trimmed, but overall organization is effective.

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 zero parameters and a simple read-only purpose, the description provides sufficient context: what is returned (prices, routes, settlement resources, free alternatives), why prices are not hardcoded, and how to call it. It does not need to detail an output schema for such a straightforward listing operation.

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 input schema is an empty object with zero parameters, so there are no parameter semantics to document. The description correctly implies no arguments are needed, and the example call guild_paid_operations() reinforces this.

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 the tool returns every paid operation with current price, exact callable entrypoint, x402 settlement resource, and free alternative. It is explicitly marked FREE and read-only, distinguishing it from the paid sibling operations it lists.

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 explicitly says to call this tool for the live price, exact route, and free alternative, and explains why prices are deliberately not hardcoded. It provides an example call. It does not explicitly compare against sibling directory tools, but the usage intent is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgentTanuki/agent-guild'

If you have feedback or need assistance with the MCP directory API, please join our Discord server