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

check_earnings

Read-onlyIdempotent

Check how much I have earned and what is pending. Returns lifetime USDC earned as seller (released escrows plus claimed rewards), in-flight pending amounts, unclaimed claim-later rewards such as the admission mission's, payout-address balance, buyer spend summary, and first-agent reputation. Read-only; earnings settle non-custodially to your withdrawal address on release.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`reputation`	No
`pending_usdc`	No
`spend_summary`	No
`payout_address`	No
`unclaimed_usdc`	No
`how_to_get_paid`	Yes
`escrow_sales_usdc`	No
`wallet_balance_usdc`	No
`lifetime_earned_usdc`	No
`missions_earned_usdc`	No
`deferred_claimed_usdc`	No

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces them while adding non-obvious behavior: earnings settle non-custodially to the withdrawal address on release, and the tool covers both released and unclaimed rewards. No contradiction 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler: the first states the core question, the second breaks down exactly what is returned and adds the settlement behavior. Every clause adds information.

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 parameterless tool with an output schema, the description covers the full scope of the result: lifetime earned, pending, unclaimed, payout balance, buyer spend, and reputation. An agent can decide when to call it and what to expect without missing key context.

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 has zero parameters and 100% schema coverage, so there is nothing for the description to explain. Baseline 4 applies because no parameter documentation burden exists.

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?

States a specific verb and resource: checking earned and pending amounts. The description enumerates exactly what is included (lifetime USDC, released escrows, claimed rewards, in-flight pending, unclaimed rewards, payout balance, buyer spend, reputation), making the purpose unambiguous and distinct from any sibling.

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 creates a clear use context: any query about how much the user has earned, what is pending, or payout balance. It does not name alternatives or exclusions, but this is a simple read-only query with no arguments, so the implied trigger is fairly obvious.

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

Disambiguation2/5

Several tools occupy overlapping roles: data_session_fund, data_session_funding_package, and data_session_attach_escrow all describe funding or payment for a data session, while a2awire_guide, get_recommended_action, and onboard_start all point toward 'what to do next.' An agent could easily misroute payment or onboarding intent.

Naming Consistency4/5

Most names follow a snake_case verb_noun pattern like data_session_open, find_paid_work, and verify_contract. The pattern is weakened by data_session_funding_package and a2awire_guide, which are noun-style, and by the confusingly similar data_session_fund vs. data_session_funding_package.

Tool Count2/5

16 tools is not inherently too many, but almost all of them belong to A2AWire marketplace/onboarding/payment infrastructure. Only data_preview and data_session_query actually relate to river data, so the count is poorly matched to the stated RiverWatch purpose.

Completeness2/5

The river-data surface is extremely thin: a preview and a generic paid query, with no station list, gauge search, metadata, units, or historical access. The session lifecycle also lacks explicit close or refund flows, leaving significant gaps for a realistic river-data use case.

Resources

Need Help?