Skip to main content
Glama

Agent Exchange store

signals_hn

$0.002 via x402: Hacker News stories by search term, newest first (Algolia HN search): title, url, points, comments, author, time, story id. Pay 0.002 USDC through https://store.agentexchange.work/gw/signals/hn?q=x402 Via the Agent Exchange store gateway; settled by Coinbase.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "signals_hn"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesq
sortNodate (default) or relevance
limitNo1..50, default 20
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the crucial behavioral trait: this is a paid tool ($0.002 USDC via x402, settled by Coinbase, through a named gateway URL). That payment/auth context is genuinely valuable. It still omits failure modes, rate limits, and what happens on an unpaid or invalid call beyond the schema's brief hint, so it is only partially complete.

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?

Front-loads the price and the core purpose, which is good, but the payment point is stated twice ('$0.002 via x402' and 'Pay 0.002 USDC') and the raw gateway URL is inlined, making it dense and slightly repetitive rather than tight.

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?

For a paid, no-output-schema tool whose 4 params are fully schema-documented, the description supplies what the schema cannot: the payment mechanism, gateway, and the list of returned fields. That is close to complete, with only sibling differentiation and error behavior missing.

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%, so the schema already documents q, sort, limit, and x_payment; baseline is 3. The description adds no syntax or format detail beyond echoing 'q' in the URL and the sort intent ('newest first'), so it does not exceed the schema.

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

Purpose4/5

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

States a specific verb+resource: 'Hacker News stories by search term, newest first (Algolia HN search)' and even lists the returned fields. This is far clearer than the name alone. However, it never names the sibling hn_top_stories, so the agent must infer the distinction (searchable feed vs. top stories) from the phrase 'by search term'.

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?

No when-to-use or when-not-to-use guidance. The description implies a keyword-search workflow via 'by search term', but with hn_top_stories as a sibling it never states the condition that selects this tool over that one, nor any prerequisites such as holding USDC/credits before calling.

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.

Resources