Skip to main content
Glama
harpd-dev

harpd-mcp

Official
by harpd-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get AI tools from the Harpd Discovery Index

get_ai_tools
Read-only

Retrieve AI tooling products from Harpd's AI Tools Index with full provenance. Filter by category, domain, or query to obtain current records including descriptions and discovery sources.

Instructions

Return AI tooling products from the Harpd AI Tools Index (693 records, Discovery Index slice where category is "agents" or "ai-media"). This is a COVERAGE list derived from the Harpd Product Discovery Index, NOT a ranking: records carry no rank and no rankPoints, and their order implies nothing about quality. Each record includes its observed_at timestamp, discovery source and profile URL. Use this to retrieve the current AI tools dataset: name, domain, URL, category, title, description, discovery source and observation timestamp. Every record carries full provenance (source, dataset path, sourceUrl, updatedAt, license, attribution).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return (1-200, default 20).
queryNoFree-text query matched against name, domain, title and description.
domainNoExact or suffix domain match, e.g. "uneed.best".
offsetNoNumber of records to skip before the page starts. Must be >= 0.
categoryNoExact Discovery Index category, e.g. "agents", "developer", "ai-media".
onRankBoardNoFilter on whether the record also appears on the Harpd Rank board.
minConfidenceNoOnly records whose category_confidence is >= this value (0-1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only and open-world behavior, and the description adds meaningful beyond-annotation context: this is a coverage list, not a ranking, records carry no rank or rankPoints, and order implies nothing about quality. It also discloses provenance behavior and returned fields.

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 moderately sized and front-loads the core purpose and scope before caveats. It is slightly repetitive in enumerating record fields and provenance twice, but every sentence contributes useful information.

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?

For a read-only list tool with strong annotations and fully documented parameters, the description covers the dataset size, category scope, non-ranking semantics, returned fields, and provenance. An agent has enough context to call it correctly without an output schema.

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 fully documents all 7 parameters. The description does not add parameter-level detail, so the baseline of 3 applies; it usefully confirms the record fields but not parameter semantics.

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?

States a specific verb ('Return') and resource ('AI tooling products from the Harpd AI Tools Index') and precisely scopes the slice by category. It also explicitly differentiates this from a ranking, which distinguishes it from sibling ranking tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly says 'Use this to retrieve the current AI tools dataset' and describes the intended data slice. It does not explicitly name alternatives or state when not to use it, but the context is strong enough for an agent to choose appropriately among siblings.

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

Deploy Server

Other Tools