CISA Known Exploited Vulnerabilities (kevwatch)

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

Behavior4/5

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

Does not contradict annotations, which show readOnly/openWorld/idempotent. Adds contextual meaning: no API key needed, returns open jobs plus a matched subset, and tells the agent to then call start_job to earn. Slight gap: no mention of pagination/rate limits, but with annotations covering safety profile this is adequate.

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?

Three punchy sentences, front-loaded with the most important operational fact (no API key needed) followed by purpose, filter guidance, and next-step action. No wasted words.

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?

Output schema exists, annotations cover safety, and description gives the full workflow entry—when to use, what it returns, what to do next. Nothing critical is missing for an agent to call it correctly.

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 baseline 3 applies. The description adds minimal new parameter meaning (case-insensitive capability, prefer testnet) but mostly restates schema info.

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?

Description clearly states a specific verb+resource: find paid work on the A2AWire job board, with filtering by capability and network. Distinguishes from siblings by emphasizing its role as the entry point before start_job.

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

Usage Guidelines5/5

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

Explicitly tells when to call: 'call this now' cold-start context, and routes next step to start_job with a job_id. Also gives filtering guidance: case-insensitive capability, prefer testnet for cold-start.

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

All CISA Known Exploited Vulnerabilities (kevwatch) 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 hazy boundaries: data_session_fund, data_session_funding_package, and data_session_attach_escrow all concern session payment/funding, and a2awire_guide overlaps with get_recommended_action as a navigation/guidance tool. Agents may easily pick the wrong call without reading descriptions carefully.

Naming Consistency4/5

Most names follow a clear snake_case verb_noun pattern such as data_session_open, find_paid_work, and verify_contract. Minor deviations like a2awire_guide, data_session_funding_package, and register keep it from being perfectly uniform, but the convention is generally predictable.

Tool Count3/5

16 tools is at the heavy edge of a normal surface, and many of the tools are generic A2AWire marketplace helpers rather than KEV-specific functionality. A dedicated KEV server would feel tighter with fewer, but the count is not extreme.

Completeness2/5

The set describes a wider marketplace but omits a referenced start_job tool, creating a dead end after find_paid_work. It also lacks any direct KEV query/metadata/session-status tool beyond the payment/session flow, so agents cannot fully complete the advertised workflows.

Resources

Need Help?