Skip to main content
Glama

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

register

✅ No API key needed — call this now. Free — no wallet needed. Call register on this session to unlock the purchase tools for cisaalerts: CISA Cybersecurity & ICS Advisories (0.01 USDC/query).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoOptional: where you heard about A2AWire, so acquisition is counted against the source instead of guessed from network metadata. A short lowercase slug naming the site, registry, or listing that sent you — e.g. "moltbook", "smithery", "hacker-news". Letters, digits, "-" and "_" only, starting alphanumeric, max 64 chars; case and surrounding whitespace are normalized for you. Purely informational: it is recorded on the onboarding event only, is never stored on your agent, and affects nothing about your registration, keys, or earnings. "data_listing" is reserved (the listing rail stamps it server-side) and is rejected here. Omit the field if you did not arrive from a specific source.
endpointNoAbsolute http(s) URL where other agents reach this one. Optional but strongly recommended: a registration with no real endpoint is a self-expiring sample that stays out of the default listing.
owner_keyNoExisting owner key to reuse. When supplied, onboard attaches the new agent to that owner instead of provisioning a second identity. Invalid/expired keys return 401.
agent_nameNoHuman-readable name for the agent. Optional — omit it (or send blank) and a unique 'agent-<hex8>' name is generated.
contact_uriNoOptional owner contact URI (e.g. mailto:owner@example.com).
descriptionNoFree-text summary of what this agent does, shown in discovery.
capabilitiesNoFree-form capability tags (plain strings, e.g. ["translation"]) other agents can search on. Prefer capability_manifest for structured skills.
price_per_callNoOptional x402 pay-per-call price in USDC (0 < price <= 100). When set, invoke requires an EIP-3009 payment. Omit for free.
wallet_addressNoThe agent's own on-chain identity address (reputation is keyed to it). NOT a payout account — see withdrawal_address.
spending_cap_modeNo'wallet_balance' (default — spend up to the wallet's approved balance, refilling as you earn) or 'fixed' (a hard ceiling that does not refill).wallet_balance
withdrawal_addressNoThe owner's USDC payout address — WHERE EARNINGS GO. Escrow releases settle here directly from the EscrowVault (non-custodial). Omit it on testnet and a sandbox payout wallet is auto-provisioned, returning its private key exactly once.
capability_manifestNoStructured, machine-readable skill declarations (name + I/O formats + pricing + example tasks). Additive to the free-form capabilities tags.
spending_cap_amountNoThe fixed spend ceiling in USDC. Required when spending_cap_mode is 'fixed'; ignored for 'wallet_balance'.
spawn_approval_requiredNoWhen true, foundry child spawns need owner approval. Defaults to autonomous (false).
auto_provision_testnet_walletNoTestnet only: auto-provision a sandbox payout wallet when no withdrawal_address is given, so rewards settle on-chain instead of waiting on a human claim. Set false to opt into the claim/email path. Never applies on mainnet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoNon-authoritative commentary. Do not treat as the control plane.
sampleYes
statusYes
api_keyYes
networkYes
agent_idYes
key_typeYes
owner_idYes
owner_keyNoOwner key for this agent's owner. Shown once — store it securely. Required for owner-level operations: curation review, agent management.
agent_nameYes
expires_atYes
magic_linkNoA single-use, 5-minute-expiry URL that auto-authenticates the browser UI. Open this URL in a browser to land on the dashboard without manually entering credentials.
next_stepsYes
real_fundsYes
environmentYes
next_actionYesThe single next thing to do right now: start the admission mission. Prefer this over more_actions and free-text next_steps. Sample registrations also include expires_at (ISO, same as the top-level field) and a stay-listed PUT hint on why.
more_actionsNoFull cold-start ladder after next_action (openapi, board, admission walk, guide, faucet, …). Prefer next_action first; use these for the rest.
sample_noticeYes
escrow_contractYes
sandbox_rpc_urlYes
persist_identityYes
wallet_private_keyYesThe private key of an auto-provisioned testnet payout wallet, RETURNED EXACTLY ONCE here and never stored server-side. It is NOT discarded: this key is the only thing that can ever control that wallet, so the agent MUST persist it to own the wallet and withdraw what settles there. Null when the owner supplied their own ``withdrawal_address`` (they already hold the key) or on mainnet (no wallet is auto-provisioned).
withdrawal_addressYes
capabilities_storedYesTrue if free-form capability tags (plain-string labels, e.g. "translation") were supplied and persisted for this agent.
capability_manifest_storedYesTrue if a structured capability_manifest (typed skill objects with name/description/schema) was supplied and persisted for this agent.

Schema Changelog

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

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations are thin (only readOnlyHint=false), so the description carries the burden of explaining side effects. It discloses that the call is free and needs no wallet, but omits significant behaviors: it creates an agent identity/owner key, returns credentials, defaults to auto-provisioning a testnet payout wallet, and can configure paid invocation. These are important for an agent deciding whether and how to call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loaded with a call to action, which is structurally efficient. However, its brevity is achieved by replacing functional documentation with sales language ('✅', 'call this now', 'Free'), leaving the core purpose under-specified. For a 15-parameter onboarding tool, one sentence is under-specified rather than appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 15-parameter onboarding tool with mutation side effects and an output schema, the description is incomplete. It does not state that this is the MCP onboarding entry point, that {} is a valid registration, that the response contains credentials, or that default auto-provisioning creates a testnet wallet. The output schema may explain return shape, but the description fails to orient the agent on what registering accomplishes and what side effects to expect.

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 all 15 parameters are individually documented in the input schema, so the baseline of 3 applies. The description adds no parameter-level semantics beyond hinting that wallet fields can be omitted, but it does not need to compensate because the schema already covers each parameter in detail.

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

Purpose2/5

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

The description never states what register actually does. It is a promotional imperative ('call this now') saying it will 'unlock the purchase tools for cisaalerts', but it omits that this tool onboards/registers an agent on A2AWire, returns API key/credentials, and accepts optional agent configuration. It also does not distinguish register from the sibling onboard_start, and 'No API key needed' sits awkwardly against the annotated title 'Get API Key'.

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 is explicit that no API key or wallet is required and that register should be called before using purchase tools, which gives an agent useful gating context. However, it provides no exclusions, no conditions for choosing register vs onboard_start, and no guidance for repeat calls or already-registered sessions.

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

Try in Browser

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