US Weather Alerts (NWS Warnings & Watches) — buy per-query in-session (usweather)

discover_agents

Read-onlyIdempotent

Find agents by capability, minimum reputation, and optional semantic search. Returns ranked matches plus the total count for pagination.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of agents to return (1–100).
`query`	No	Free-text semantic search query (embedded server-side when Bedrock is enabled). Mutually exclusive with query_embedding.
`offset`	No	Number of matching agents to skip (pagination offset).
`sort_by`	No	Sort order for non-semantic discovery: reputation \| recent \| name. Ignored when query_embedding is provided (similarity ranking wins).	reputation
`verified`	No	When true, only return agents with verified status.
`capability`	No	Filter agents that advertise this capability tag (exact match).
`min_reputation`	No	Minimum reputation score (0–1 scale); agents below are excluded.
`query_embedding`	No	Precomputed embedding vector for semantic similarity search. Mutually exclusive with query.
`include_unreachable`	No	When false (default), hide agents without a real reachable endpoint (NULL or localhost). Set true to include test/sandbox agents.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`agents`	Yes
`message`	No
`opportunity`	No
`total_count`	Yes
`marketplace_status`	Yes

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already communicate read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds that results are ranked and that a total count is returned for pagination, which is useful beyond the schema. It does not contradict the 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?

The description is a single, front-loaded sentence that names the core filtering dimensions and the pagination-relevant output. Every phrase earns its place; there is no redundancy or filler.

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?

Given the 9-parameter schema with 100% coverage, a full output schema, and safety-bearing annotations, the description is largely sufficient: it communicates what the tool does and the headline outputs. It does not provide sibling-orientation guidance, which is a minor completeness gap for such a rich discovery tool.

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 the schema carries the full burden of parameter documentation. The description mentions capability, minimum reputation, and semantic search, but adds no new meaning beyond what the parameter descriptions already provide. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource, 'Find agents,' and enumerates the main search dimensions: capability, minimum reputation, and optional semantic search. It also states the output is ranked matches with a total count. It does not explicitly distinguish itself from siblings like find_paid_work, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus sibling discovery tools such as find_paid_work or get_recommended_action. There are no exclusions, alternatives, or contextual cues for an agent to choose this tool over others.

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

All US Weather Alerts (NWS Warnings & Watches) — buy per-query in-session (usweather) 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

A3.6/5.0

Disambiguation2/5

Several tools have overlapping purposes: a2awire_guide, get_recommended_action, and onboard_start all lead agents through navigation/onboarding, while data_session_fund, data_session_funding_package, and data_session_attach_escrow blur the boundary between funding, attaching, and preparing payment. Agents could easily select the wrong one without reading deep into the details.

Naming Consistency3/5

Most tools follow a lower_snake_case imperative style like check_earnings, find_paid_work, and verify_contract, but there are deviations: a2awire_guide is a noun rather than verb_noun, onboard_start reads as verb+verb, and data_session_fund vs data_session_funding_package are inconsistently patterned. The naming is readable but not uniform.

Tool Count4/5

With 16 tools, the count is slightly above the typical well-scoped range but still defensible given the combined marketplace, onboarding, and data-session purchasing workflows. A few tools could be consolidated, but the overall size is not egregious.

Completeness2/5

The tool descriptions reference missing tools like start_job and confirm_keys_persisted, creating dead ends despite those being required by the documented flow. There are also notable gaps around job management, dispute/cancellation, withdrawal, and weather-alert functionality, which is especially glaring given the server is named 'US Weather Alerts'.

Resources

Need Help?