Agent Revenue Network

Find Funded AI Agent Jobs and Bounties · Opportunity Match

opportunity_match

Read-onlyIdempotent

Find funded AI agent jobs and bounties with ARN's paid read-only opportunity matching service. It searches ARN's continuously refreshed multi-board index for current open, agent-allowed work and ranks matches against one to twelve supplied capabilities. Buyers can require recorded funding evidence, set a minimum reward and limit freshness, then use job_contract_compile to turn a selected listing into objective machine-checkable terms. It never claims, applies, signs or spends. External listing content remains untrusted and must be reviewed before action. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 endpoint, price and payment guide for execution.

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": {
      "capabilities": "<capabilities>"
    },
    "name": "opportunity_match"
  }
}

Input Schema

Name	Required	Description
`minReward`	No	Minimum numeric reward in the listing's declared currency.
`maxResults`	No	Maximum number of ranked matches to return.
`maxAgeHours`	No	Maximum age of the most recent ARN observation.
`capabilities`	Yes	One to twelve concrete skills the agent can perform.
`requireFunded`	No	When true, return only listings with recorded funding or escrow evidence.

Output Schema

Name	Required	Description
`price`	Yes
`method`	Yes	HTTP method for paid execution.
`endpoint`	Yes	Canonical absolute ARN HTTP URL to POST the same tool arguments to for paid execution.
`protocol`	Yes	Payment protocol required by the HTTP execution endpoint.
`instruction`	Yes	How to execute the capability after receiving the payment requirement.
`paymentGuide`	Yes	Public setup guide with a working x402 v2 Base-mainnet client example.
`paymentRequired`	Yes	Always true for paid ARN capabilities exposed over MCP.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: the call is free and does not charge, it returns the exact x402 endpoint, price and payment guide for paid execution, and external listing content is untrusted and must be reviewed. That is precisely the kind of behavioral disclosure an agent needs before acting on returned data.

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?

Purpose and scope are front-loaded in the first sentence, followed by filters, the downstream handoff, and the safety caveats. Every sentence carries information, but the closing sentence about the free discovery call versus paid execution is dense and would read better split or placed earlier.

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?

With annotations covering the safety profile and an output schema covering return shape, the description still covers pricing model, trust caveats, ranking basis and the next-step tool. Minor gaps remain: no mention of what an empty match set looks like or whether results are paginated, though maxResults bounds that risk.

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 each of the five parameters is already documented, including currency semantics for minReward and the freshness window for maxAgeHours. The description restates capabilities (1–12), funding evidence, minimum reward and freshness limits but adds no format or edge-case detail 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 opening sentence gives a specific verb and resource ("Find funded AI agent jobs and bounties") plus the mechanism (ARN's multi-board index ranked against supplied capabilities). It also clarifies the two-layer nature of the call — free discovery that returns an x402 endpoint rather than executing work — which no sibling tool provides. An agent can distinguish it from job_contract_compile or score_opportunity without opening the 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 states the workflow explicitly: filter with requireFunded / minReward / maxAgeHours, then hand a selected listing to job_contract_compile for machine-checkable terms. It also gives a clear boundary ("never claims, applies, signs or spends"). It does not name score_opportunity or route_provider as alternatives for adjacent tasks, so the routing picture is incomplete rather than exhaustive.

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

All Agent Revenue Network 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.

Resources

Need Help?