Skip to main content
Glama

npm Release Tracker — new Node.js packages & JavaScript dependency updates (npmwatch)

register

✅ No API key needed — call this now. Free — no wallet needed. Call register on this session to unlock the purchase tools for npmwatch: New npm package releases & JavaScript dependency updates (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?

The description adds context beyond annotations: it discloses there is no auth prerequisite ("No API key needed"), no cost ("Free"), and no wallet requirement — useful guardrails given the annotations carry no positive hints. But it fails to disclose what the registration actually does (provisions an agent identity, may auto-provision a sandbox payout wallet returning a private key exactly once, sets spending caps, returns an API key). No contradiction with annotations exists; readOnlyHint=false is consistent with a registration mutation.

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 (~30 words) and front-loads the actionable claim, but it is a run-on marketing pitch with emojis and urgency framing ("✅", "call this now"). The product advertisement "New npm package releases & JavaScript dependency updates (0.01 USDC/query)" is promotional noise that displaces functional specification of the tool being described.

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

Completeness3/5

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

Given the output schema exists and the input schema covers all 15 parameters exhaustively, the description's burden is narrowed to purpose and side effects — and there it is thin: it never mentions what the call returns (API key), the onboarding flow for wallet/earnings, or how it relates to onboard_start. For the narrow 'unlock npmwatch' scenario it suffices, but it under-prepares the agent for the tool's actual complexity and side effects.

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 each of the 15 parameters carries a rich, self-contained explanation (including the SpendingCapMode and CapabilityManifest $defs), so the baseline of 3 applies. The description contributes zero parameter information, but it is not required to because the schema already does the heavy lifting.

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

Purpose3/5

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

The description states a concrete actionable outcome ("Call register on this session to unlock the purchase tools for npmwatch"), so the immediate purpose is legible. However, it never states the tool's actual system function — agent onboarding/registration on A2AWire (agent identity, wallet, capabilities, pricing) — and the annotation title "Register / Get API Key" reveals key issuance that the description omits. An agent could reasonably mistake this for an npmwatch-specific unlock rather than a general onboarding tool.

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

Usage Guidelines2/5

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

The directive "No API key needed — call this now" gives an explicit call-to-action but offers no real usage guidance: no conditions, no exclusions, and no distinction from the sibling onboard_start (which the schema describes as the other onboarding door via REST POST /api/v1/onboard). The only implied use case is "when you want npmwatch purchase tools," leaving the agent to guess when the broader onboarding surface is appropriate.

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 overlapping guidance and discovery purposes: a2awire_guide, get_recommended_action, find_paid_work, discover_agents, and hire_and_execute all point toward finding/doing work. data_session_fund and data_session_funding_package are especially easy to confuse, and the many escrow/session tools blur together.

Naming Consistency2/5

Naming is mixed: some tools use data_session_* consistently, while others use bare verbs (register, verify_contract), noun phrases (check_earnings, discover_agents), or verb_and_verb (hire_and_execute, find_paid_work). The distinction between data_session_fund and data_session_funding_package is not clear from names alone.

Tool Count2/5

16 tools is excessive for a server presented as an npm release tracker, especially since only data_preview and data_session_query actually relate to npm data. Most of the surface is an unrelated A2AWire marketplace/escrow platform, making the server feel bloated and off-purpose.

Completeness2/5

The npm-facing surface is thin: one preview and one generic query tool, with no direct listing, search, or filter tools exposed. The A2AWire workflow also has gaps: find_paid_work mentions start_job but that tool is not provided, and check_earnings mentions unclaimed rewards with no claiming tool.

Resources