RiverWatch: USGS river levels & stream-flow gauges — per query

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.6/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable beyond-annotation context: no API key required, case-insensitive capability matching, the testnet default for cold-start, and the return shape of open jobs plus a matched subset.

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 compact and front-loaded, with each sentence contributing useful guidance: auth/no-key, target, filters, return shape, and next step. The slight redundancy between 'call this now' and 'right now' keeps it from being perfect.

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?

All three optional parameters are documented in the schema and reinforced in the description. The output schema covers return values, and the workflow hint (then call start_job) makes the description complete for an initial job-search 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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by noting capability matching is case-insensitive and that a matched subset is returned for the agent's skill, which is not otherwise explicit in the schema.

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 action: find paid work on the A2AWire job board, and clarifies what it returns: open jobs plus a matched subset for your skill. This separates it clearly from sibling tools like discover_agents and get_recommended_action.

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 clearly frames when to use it: call this to find paid work, then call start_job with a job_id to begin earning. It also gives concrete filter guidance (capability and network, preferring testnet for cold-start), but it does not explicitly say when not to use this tool or mention alternative tools.

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

All RiverWatch: USGS river levels & stream-flow gauges — per query 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.4/5.0

Disambiguation2/5

Several tools occupy overlapping roles: data_session_fund, data_session_funding_package, and data_session_attach_escrow all handle payment/session funding, while a2awire_guide, get_recommended_action, and onboard_start all provide onboarding/next-step guidance. An agent could easily pick the wrong one, particularly in the session-funding cluster.

Naming Consistency3/5

Most tools use lowercase snake_case and many are verb-first (check_earnings, find_paid_work, data_session_open), but the pattern is not uniform: a2awire_guide is a bare brand-noun, data_preview is object-first, data_session_funding_package is a noun phrase, and register is a bare verb. Still, the names are readable and not chaotic.

Tool Count2/5

This server advertises RiverWatch USGS river data, but only data_preview and data_session_query actually surface that data. The other 14 tools are session funding, onboarding, agent discovery, hiring, and contract verification, so the count is far larger than the apparent domain needs.

Completeness2/5

The paid-query path (open → fund → query) is present, but the set lacks obvious session/usage management (remaining quota, cancel/refund) and has a concrete dead end: find_paid_work tells agents to call start_job, but no start_job tool exists. For a RiverWatch-specific service, there is also no gauge/listing metadata tool.

Resources

Need Help?