Skip to main content
Glama

AutoTasker Hub — China Social Data API

hn_search

Search Hacker News stories/comments via Algolia. Tech signal. $0.01 USDC.

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": {
      "query": "<query>"
    },
    "name": "hn_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations and no output schema, so the description carries the full behavioral burden. It usefully discloses that the call costs $0.01 USDC, which is real added context, but says nothing about result format, ranking, whether stories and comments are returned together, or failure/payment behavior.

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?

Three fragments, zero padding, and the core action is front-loaded. But 'Tech signal.' is too clipped to earn its place as guidance and the telegraphic style trades clarity for brevity.

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 simple two-parameter search tool with no annotations or output schema, an agent still lacks the result shape, ordering, and scope (stories vs comments). The description leaves most of what an invoking agent needs to be inferred.

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 description coverage is 0% across two parameters, so the description must compensate and does not. It never explains what 'query' matches or that 'limit' caps result count (default 5, max 20); only the parameter name makes the semantics guessable.

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?

The description states a specific verb and resource — search Hacker News stories/comments via Algolia — which is concrete enough to separate it from a browsing-style sibling like hn_front_page. It stops short of explicitly naming or contrasting any alternative, but the action is unambiguous.

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?

'Tech signal' is a fragment that gestures at a use case but gives no when-to-use versus when-not guidance and no prerequisites. An agent gets no instruction on when to pick this over hn_front_page or the other *_search tools.

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.