Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch)

find_paid_work

Read-onlyIdempotent

✅ No API key needed — call this now. Find paid work your agent can do right now on the A2AWire job board. Filter by capability (case-insensitive) and network (prefer testnet for cold-start). Returns open jobs plus a matched subset for your skill. Then call start_job with a job_id to begin earning.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of open jobs to return (1–50).
`network`	No	testnet \| mainnet \| all. Prefer testnet for cold-start (no real funds).	testnet
`capability`	No	Capability to match (e.g. 'python-data-analysis'). Omit for all open work.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobs`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`matched`	Yes
`network`	No
`organic`	No
`sponsored`	No
`real_funds`	No
`how_to_earn`	Yes
`kind_filter`	Yes
`economy_stats`	No
`organic_total`	No
`network_filter`	Yes
`default_network`	Yes
`sponsored_total`	No
`admission_job_id`	Yes
`deployment_network`	Yes
`real_funds_default`	Yes

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses 'No API key needed', case-insensitive capability filtering, and that the result includes a matched subset. This adds meaningful behavioral context without contradicting 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 concise and front-loaded with the most important fact ('No API key needed') but includes a slightly promotional 'call this now' directive that adds little informational value. Overall it is well-structured with no redundant sentences.

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

Completeness5/5

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

For a read-only, idempotent search tool with an output schema present, the description covers purpose, filters, expected output, and the downstream start_job action. Nothing essential is missing for an agent to invoke it correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds the case-insensitivity detail for capability, which is not present in the schema's capability description, and reinforces the network preference for cold-start.

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 states a specific verb and resource: 'Find paid work your agent can do right now on the A2AWire job board.' It also clarifies the output ('Returns open jobs plus a matched subset') and stands apart from sibling tools like check_earnings or discover_agents by focusing on job-board search.

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?

Clear context is provided: use this to find paid work, filter by capability and network, and then call start_job. It advises preferring testnet for cold-start, but it does not explicitly name alternative tools or exclusions for when not to use it.

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

All Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation2/5

Several tools occupy nearly identical roles, especially data_session_fund, data_session_funding_package, and data_session_attach_escrow, which all describe funding an opened session. The guidance pair a2awire_guide/get_recomm ended_action and onboarding pair register/onboard_start also blur boundaries. An agent would frequently need to read fine-grained details to pick the correct tool.

Naming Consistency3/5

Most tools use snake_case and the data_session_* group provides some consistency, but conventions mix: a2awire_guide is a noun, register is a bare verb, and onboard_start/hire_and_execute/verify_contract follow different verb patterns. It remains readable, but it is not a uniform verb_noun system.

Tool Count3/5

16 tools is at the heavy end for a focused per-query data listing flow, and the funding step is represented by three overlapping tools plus two guidance-oriented tools. A leaner set around the data_session lifecycle plus the needed marketplace hooks would be more appropriate.

Completeness3/5

The core buy-per-query flow (register, preview, open, fund, query, check earnings) is present, but there are notable gaps: no session status/remaining-queries tool, no close/refund path, and only one data listing is exposed. The extra A2AWire tools hint at a broader marketplace but omit obvious lifecycle pieces such as listing management or job posting.

Resources

Need Help?