Skip to main content
Glama

Product Hunt Launches — new & upcoming products (producthuntwatch)

register

✅ No API key needed — call this now. Free — no wallet needed. Call register on this session to unlock the purchase tools for producthuntwatch: new Product Hunt launches, hourly (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

D1.3/5.0
Behavior1/5

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

With readOnlyHint=false and no other safety signals, the description carries the burden of disclosing side effects, yet it discloses none: registration provisions an agent identity, may auto-provision a testnet wallet that returns its private key once, and can attach pricing and spending caps. Its claim that 'no wallet needed' directly clashes with the schema's wallet_address, withdrawal_address, and escrow semantics.

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

Conciseness2/5

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

The description is short and front-loaded, which is structurally fine, but both sentences are promotional noise that displace real information about the tool. Compactness without substance — emojis and a price tag ('0.01 USDC/query') — does not earn the space it occupies.

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

Completeness1/5

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

For a 15-parameter mutating tool with minimal annotations, the description needed to explain what registration produces (per the annotation title, an API key), what side effects occur, and when it applies. It explains none of this and instead describes an unrelated Product Hunt data-query service, leaving the agent unable to form a correct mental model of the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with rich per-field descriptions, so the baseline is 3 and the description need not repeat parameter details. However, the description actively undermines the schema by implying a no-setup call ('Free — no wallet needed'), which misrepresents the 15-parameter surface; that negative value drops it below baseline.

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

Purpose1/5

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

The description claims register 'unlock[s] the purchase tools for producthuntwatch: new Product Hunt launches, hourly (0.01 USDC/query)', but the input schema is OnboardRequest — a generic agent-registration tool with fields for agent name, endpoint, capabilities, and wallet/escrow setup. It pitches a specific product offering instead of stating the tool's actual function, so an agent would be actively misled about what register does.

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

Usage Guidelines1/5

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

'No API key needed — call this now' is an unconditional promotional directive with no when-to-use/when-not-to-use guidance and no mention of the sibling onboard_start as the alternative onboarding path. The instruction is also misleading: it frames the call as a free no-setup unlock, whereas the schema describes a registration that establishes an agent identity with optional payment and wallet configuration.

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

C2.9/5.0
Disambiguation2/5

Several tools overlap in purpose: a2awire_guide, get_recommended_action, and onboard_start all tell the agent what to do next, while data_session_fund, data_session_funding_package, and data_session_attach_escrow blur the payment/funding steps. Agents could easily select the wrong navigator or funding tool without careful reading.

Naming Consistency3/5

Most tools follow an imperative verb_noun pattern like check_earnings, discover_agents, and hire_and_execute, but a2awire_guide and data_session_funding_package are noun phrases. The data_session_ prefix provides some structure, yet fund/funding_package/open/query mix verb and noun styles.

Tool Count3/5

16 tools is at the high end of a reasonable range, but the set feels heavier than the server's Product Hunt focus warrants. Many tools cover unrelated A2AWire marketplace operations like agent discovery, hiring, and onboarding, making the count feel inflated for a launch-data listing.

Completeness3/5

The core paid data-access flow is covered end-to-end: preview, register, open session, fund, and query. However, there are notable gaps like session cancellation/refunds, explicit withdrawal, and broader A2AWire lifecycle management such as unregistering an agent.

Resources