Skip to main content
Glama
Sign In

acdoyle

by io.github.granetb-acdoyle
OverviewDiscussionsAdmin

Server Details

Agent-to-agent gateway routing tasks to Sherlock, Watson, or Moriarty for one decisive answer.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
granetb-acdoyle/acdoyle
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation3/5

The two tools perform the identical core action (dispatch a task to acdoyle and return one answer) and differ only in payment mechanism (metered api_key vs x402 protocol). The descriptions clearly explain the distinction, but the overlapping purpose means an agent must reason about payment method rather than task intent, which is a non-trivial selection decision.

Naming Consistency4/5

Both names share the acdoyle_ prefix and a consistent verb_noun base (acdoyle_dispatch, acdoyle_dispatch_x402). The x402 suffix is a reasonable variant marker for the payment-gated form, though it slightly breaks the uniform pattern.

Tool Count3/5

Two tools is borderline thin for a gateway that also involves credit metering, personas, and payment challenges. The surface is defensible for a minimal dispatch API but leaves little room for the surrounding account/payment lifecycle.

Completeness2/5

Only dispatch operations exist, with no tools to check credit balance, view metering/usage, manage an api_key, list personas, or complete/verify an x402 payment status. These are significant gaps for a paid gateway whose usage flow (top up at an external site) is entirely outside the tool surface.

Available Tools

2 tools
acdoyle_dispatchacdoyle dispatchAInspect

Send a task to acdoyle, an agent-to-agent gateway. acdoyle routes the task to one of three specialist personas (Sherlock: general decisive research/recommendation; Watson: budget execution and allocation, currently simulated; Moriarty: monetization/opportunity advice) and returns one confident, non-hedged answer. Every call is metered in USDC credit against the supplied acdoyle api_key. Get an api_key and top up credit at https://acdoyle.dev.

Inputs: task (required), api_key (required).

acdoyle_dispatch_x402acdoyle dispatch (x402, no api_key)AInspect

Send a task to acdoyle, an agent-to-agent gateway, with no pre-issued api_key required. acdoyle routes the task to one of three specialist personas (Sherlock: general decisive research/recommendation; Watson: budget execution and allocation, currently simulated; Moriarty: monetization/opportunity advice) and returns one confident, non-hedged answer. This call is gated by the x402 payment protocol instead of a metered api_key: the underlying HTTP request may come back as an HTTP 402 with a payment-required challenge (price, network, and payment details) instead of a result. If that happens, this tool returns isError: true with the 402 challenge details in its content — the MCP client's own HTTP layer (or the calling agent) must complete the x402 payment (sign and attach the payment header) and retry the call for it to succeed. Currently Base Sepolia testnet only.

Inputs: task (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    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