CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts)

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

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds behavioral value beyond those annotations by explaining that results are ranked and that a total count is returned for pagination, which is not obvious from the schema alone.

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, information-dense sentence with no filler. Key filters are front-loaded and the pagination behavior is stated in the second clause, making it easy to scan.

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 rich input schema, full parameter documentation, and robust annotations, the description covers the essential behavior of a read-only search tool. The output schema is present, so the description does not need to enumerate return fields; mentioning ranking and total count is enough for effective use.

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?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description summarizes capability, reputation, and semantic search, which aligns with the main parameters, but it adds no deeper meaning beyond what the schema already 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 names a specific verb ('Find'), a clear resource ('agents'), and the key filtering dimensions: capability, minimum reputation, and optional semantic search. It also states the return shape (ranked matches and total count), making it distinct from siblings like find_paid_work.

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

Usage Guidelines3/5

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

The description implies when to use the tool—whenever an agent needs to discover agents by capability or reputation—but it does not explicitly mention alternatives or when not to use it. There are no prerequisites, which fits a read-only search tool, but exclusions are absent.

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

All CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts) 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.1/5.0

Disambiguation2/5

Multiple tools have unclear boundaries: data_session_fund, data_session_funding_package, and data_session_attach_escrow all deal with funding a session, while a2awire_guide, get_recommended_action, and onboard_start overlap as guidance/onboarding helpers. An agent would struggle to pick the right tool without reading every description closely.

Naming Consistency4/5

Tool names are uniformly snake_case and mostly follow a verb_noun or data_session_* patttern. Minor deviations like a2awire_guide and data_session_funding_package lack a clear verb, but the overall style is predictable and readable.

Tool Count3/5

16 tools is at the heavy end of a reasonable range, but many are generic A2AWire platform tools such as register, discover_agents, find_paid_work, and verify_contract. The count feels inflated for a server supposedly focused on CISA cybersecurity advisories.

Completeness2/5

The server name promises CISA Cybersecurity & ICS Advisories, yet there is no direct advisory listing, search, or fetch tool—only a generic data_session_query and a free preview. The platform/session lifecycle is partially covered, but the actual advisory domain has severe gaps that would force agents to rely on a single opaque query tool.

Resources

Need Help?