Skip to main content
Glama

FoxAPIs data sources

Show HN best time

showhn_best_time
Read-onlyIdempotent

The share of Show HN posts that reached 50 and 100 points overall, for the best hour and day, and for one weekday and hour (UTC). Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "showhn_best_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourNoHour in UTC, 0 to 23
weekdayNoDay of the week in UTC, 0 = Sunday

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, and the description adds real operational context beyond them: 1 credit per call, no charge for empty answers, and the FoxAPIs key requirement. It does not describe pagination or result shape, but for a stat lookup that gap is minor.

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 metric and breakdowns are front-loaded, followed by two compact sentences on cost and key. Slightly dense phrasing in the first sentence costs it a point, but there is no filler.

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

Completeness5/5

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

With no output schema, the description still conveys what is returned (share reaching 50 and 100 points across time slices), the cost model, and the auth requirement. An agent has everything needed to call it correctly.

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 coverage is 100%, with hour documented as 0-23 UTC and weekday as 0=Sunday. The description adds that passing these yields a breakdown 'for one weekday and hour (UTC),' clarifying the filter intent, but offers no extra syntax or default behavior beyond 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?

The description names the specific metric (share of Show HN posts reaching 50 and 100 points) and the breakdowns it returns (best hour and day, plus one weekday/hour in UTC). It is clearly a Show HN timing-statistics tool, distinguishable from the sibling showhn_post_outcome, though the sentence is dense and the verb is only implied.

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?

Usage is only implied: an agent can infer this is for finding the best time to post on Show HN. There is no explicit when-to-use versus when-not guidance or naming of alternatives, though the cost and key requirements are stated.

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