Skip to main content
Glama
Sign In

MCP Harbor Search

by app.mcpharbor
OverviewDiscussionsAdmin

Search MCP Harbor

search_tools
Read-only

Search the MCP Harbor directory of MCP servers, clients and SDKs by keyword, optionally filtered by category. Returns the best matches ranked by relevance and GitHub stars. Alias of search_servers.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeywords, e.g. "postgres", "browser automation", "slack"
categoryNoOptional category slug: search-web, ai-agent-frameworks, cloud-infra, browser-automation, databases, memory-knowledge, other, productivity, developer-tools, finance-crypto, media-design, mcp-clients
remote_onlyNoIf true, only listings that publish an HTTPS remote URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional category slug: search-web, ai-agent-frameworks, cloud-infra, browser-automation, databases, memory-knowledge, productivity, developer-tools, finance-crypto, media-design, mcp-clients, other"New value: +"Optional category slug: search-web, ai-agent-frameworks, cloud-infra, browser-automation, databases, memory-knowledge, other, productivity, developer-tools, finance-crypto, media-design, mcp-clients"
    • addedInput schema / properties / remote_only
      Added value: +{
+  "description": "If true, only listings that publish an HTTPS remote URL",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional category slug: search-web, ai-agent-frameworks, cloud-infra, browser-automation, databases, memory-knowledge, productivity, developer-tools, finance-crypto, media-design, other"New value: +"Optional category slug: search-web, ai-agent-frameworks, cloud-infra, browser-automation, databases, memory-knowledge, productivity, developer-tools, finance-crypto, media-design, mcp-clients, other"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds that results are ranked by relevance and GitHub stars, but does not discuss limits, result shape, or remote_only behavior.

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?

The description is two compact sentences with no wasted wording. Core purpose and return-ranking behavior are front-loaded and easy to scan.

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 read-only search tool with good annotation coverage and no output schema, the definition gives enough context to select and invoke it. A little more on alias behavior or result limits would make it fully complete.

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 75%, with query, category, and remote_only documented in the input schema. The description reinforces keyword and category filtering but adds no new meaning for limit or remote_only, so it meets the baseline without compensating further.

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 the MCP Harbor directory of servers, clients, and SDKs by keyword. It also clarifies that this is an alias of search_servers, which helps distinguish it from non-alias siblings, though the alias relationship itself is not fully explained.

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 implied by the keyword search and optional category filter, and the alias statement suggests equivalence with search_servers. However, there is no explicit guidance on when to choose this tool over search_servers or other sibling tools.

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

All MCP Harbor Search toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources