hackyeaster-solver

he_discover_challenges

Scrape hackyeaster.com to retrieve a list of challenges with titles, URLs, descriptions, and embedded data. Use headless browsing for JavaScript-rendered content.

Instructions

Scrape hackyeaster.com and return a list of available challenges with titles, URLs, descriptions, and embedded data.

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": "he_discover_challenges"
  }
}

Input Schema

Name	Required	Description	Default
`dynamic`	No	Use headless browser (DynamicFetcher) for JS-rendered content. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the full burden falls on the description. It discloses that the tool scrapes a remote website, but does not mention potential side effects like network latency, rate limiting, or dynamic content behavior. The parameter 'dynamic' is described in the schema but not in the tool description.

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 description is concise (one sentence) and front-loaded with the main action. However, it could benefit from a more structured format (e.g., listing returned fields explicitly) to improve readability.

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?

For a tool with one parameter and no output schema, the description is fairly complete in stating the input and output. However, it lacks details about what 'embedded data' means, error handling, or behavior when the website is unreachable, which would be useful for an agent.

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?

The input schema has 100% description coverage for the single boolean parameter 'dynamic'. The tool description does not add additional semantic information about the parameter beyond what the schema already provides, so a baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool scrapes hackyeaster.com and returns a list of challenges with specific fields (titles, URLs, descriptions, embedded data). It distinguishes itself from sibling tools like he_fetch_challenge, which fetches a single challenge, and others that are unrelated to discovery.

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?

The description implies using this tool to get the full list before using other challenge-specific tools, but it does not explicitly state when to use it versus alternatives like he_fetch_challenge or he_search. No exclusion conditions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server