Skip to main content
Glama

Dependency Vulnerability Tracker — package security advisories ($0.01/query)

register

✅ No API key needed — call this now. Free — no wallet needed. Call register on this session to unlock the purchase tools for ghsawatch: package dependency vulnerabilities + malicious-package 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.8/5.0
Behavior3/5

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

Annotations are sparse (all hints false), so the description carries the burden and does add useful behavioral context: no auth prerequisite, no payment prerequisite, session-scoped effect, and the 0.01 USDC/query cost of the unlocked tools. But it omits the tool's actual side effects — registering an agent, provisioning an API key (per the title), possible wallet auto-provisioning with a private key returned once — and says nothing about repeated-call behavior. No contradiction with the annotations (readOnlyHint=false matches a write/registration operation).

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

Conciseness4/5

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

The description is compact (~33 words), front-loaded with the most actionable signal ('call this now'), and each clause carries information (no key, no wallet, what gets unlocked, cost). Minor deductions for the promotional tone and emojis, which are unusual in a tool definition but don't waste tokens.

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 15-parameter onboarding tool with a sibling onboarding door, the description leaves major gaps: it doesn't explain that this registers the agent in the network, that '{}' is a valid minimal registration, or how register relates to onboard_start. It also creates tension by saying 'no wallet needed' while the schema exposes wallet_address, withdrawal_address, and spending-cap fields. The rich schema and output schema compensate partially, but the tool-level description fails to orient the agent.

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 the schema's own parameter descriptions are exceptionally detailed (spending_cap_mode explains wallet_balance vs fixed; withdrawal_address warns 'WHERE EARNINGS GO' and notes the private-key-once behavior). Baseline 3 is appropriate; the description adds no parameter-level meaning and doesn't need to.

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 reads as call-to-action marketing ('✅ No API key needed — call this now') rather than a definition of the tool's function. It frames the purpose narrowly as 'unlock the purchase tools for ghsawatch', but the tool is actually the general agent onboarding/registration door (per the OnboardRequest schema and the 'Register / Get API Key' title), including identity provisioning, capabilities, and pricing fields. An agent must infer the real function from the title and schema rather than the description.

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 gives clear context for one scenario: call first ('call this now'), no prerequisites ('no API key needed', 'no wallet needed'), session-scoped, before using ghsawatch purchase tools. However, it gives no exclusions, no when-not-to-use guidance, and no differentiation from the sibling onboard_start, which appears to be the other onboarding door — an agent choosing between these two gets no help.

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

Multiple tools overlap in purpose: data_session_fund, data_session_funding_package, and data_session_attach_escrow all describe payment/funding steps, while a2awire_guide and get_recommended_action both provide guidance. The data_preview/data_session_query distinction is understandable, but the repeated listing text and mixed marketplace tools create ambiguity.

Naming Consistency3/5

Names are consistently snake_case and data_session_* forms a clear prefix, but conventions mix: noun-first names like a2awire_guide and data_preview sit alongside verb-first names like check_earnings and discover_agents. Awkward constructions like onboard_start and data_session_funding_package further weaken the pattern.

Tool Count4/5

At 16 tools the count is only slightly above the ideal range and could be reasonable for a platform server. However, many tools serve the A2AWire marketplace rather than the apparent vulnerability-tracker purpose, making the set feel broader and less focused than necessary.

Completeness2/5

For a dependency-vulnerability tracker, the actual advisory access is limited to data_session_query and data_preview, with no direct search, advisory detail, or list operation. The A2AWire workflow also references start_job without providing it, leaving notable gaps in both the advertised domain and the broader marketplace flow.

Resources