hacklist-mcp

Fetch HackList listing (connector)

fetch

Read-onlyIdempotent

Retrieve full HackList opportunity details by listing ID from search for ChatGPT connectors and deep research.

Instructions

Fetch the full HackList listing for an id returned by search. (Compatibility tool for ChatGPT connectors and deep research.)

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Listing id from search

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the useful context that this is a compatibility shim and that it returns the 'full' listing, but says nothing about error behavior for stale/unknown ids or response size.

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

Conciseness5/5

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

Two short sentences, front-loaded with the core action and the input constraint, with the compatibility note demoted to a parenthetical. Nothing is wasted.

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 single-parameter read tool with full annotation coverage and no output schema, the description gives enough to invoke it correctly. It could be stronger by clarifying how it differs from get_opportunity, but nothing essential is 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 coverage is 100% and the schema already documents the single 'id' parameter as coming from search, which the description merely restates. Baseline 3 is appropriate since the description adds no format, validation, or provenance detail 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?

States a specific verb and resource ('Fetch the full HackList listing') and pins the input to 'an id returned by search', so the agent knows this is an id-based retrieval, not a discovery call. It does not, however, address the obvious overlap with the sibling get_opportunity, so sibling differentiation is left implicit.

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?

'for an id returned by search' implies the correct upstream call and the parenthetical indicates the tool's niche (connector/deep-research compatibility). But there is no explicit when-to-use or when-not-to-use guidance versus get_opportunity or search, so an agent must infer the routing.

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

Deploy Server