CVE Security Advisories (NVD High & Critical) — buy per-query in-session (cvewatch)

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

A4.1/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, lowering the bar for the description. The description adds useful context about ranked results and pagination count, but it does not disclose behaviors such as default filtering of unreachable agents or sorting interactions; these are left to the schema.

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 short sentences carry the core purpose and output shape with no filler or redundancy. The most important information is front-loaded, and nothing in the description repeats schema details unnecessarily.

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?

Given the rich input schema, the output schema, and the safety-focused annotations, the description is complete enough for tool selection and invocation. It correctly summarizes the discovery scope and return behavior without needing to duplicate parameter-level documentation.

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%, and every parameter already has a detailed meaning in the schema. The description adds only a high-level summary of capability, reputation, and semantic search, without contributing new parameter-level insight beyond what the schema provides.

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 clearly states the tool's job: find agents, using capability, reputation, and semantic search. It also specifies the return shape (ranked matches and total count), making the purpose unambiguous and distinct from sibling tools focused on work, contracts, or actions.

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 gives clear context that this is the discovery/search entry point for agents, with filters and semantic matching. It does not explicitly name alternatives or spell out when not to use it, but the stated behavior is specific enough to imply the intended use case.

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

All CVE Security Advisories (NVD High & Critical) — buy per-query in-session (cvewatch) 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

Disambiguation3/5

A few clusters could cause misselection: data_session_fund, data_session_funding_package, and data_session_attach_escrow all involve paying for data sessions, and both a2awire_guide and get_recommended_action provide next-step guidance. However, most tools target distinct resources and actions, and the detailed descriptions help resolve most ambiguity.

Naming Consistency2/5

Names fall into two competing styles: verb-first commands like discover_agents/find_paid_work/get_agent_contract, and resource-first names like data_preview/data_session_open/data_session_funding_package. Within the data_session_* family, forms are inconsistent (fund vs funding_package vs attach_escrow), and a2awire_guide/onboard_start don't follow either pattern.

Tool Count3/5

16 tools is at the borderline/heavy end but not unreasonable for a platform spanning onboarding, discovery, hiring, escrow, and data-session payments. The count feels inflated mainly because much of that scope is unrelated to the server's advertised CVE-advisory purpose.

Completeness1/5

The server name promises CVE Security Advisories from NVD, yet there is no CVE-specific search, list, get, or filter tool. The only query path is generic data_session_query, which could target any data listing, so an agent cannot reliably accomplish the server's core advertised workflow.

Resources

Need Help?