Skip to main content
Glama

search_projects

Search the PostLaunchKit directory of reviewed free tools and projects, including AI agent tooling. Returns published entries only.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
pageNo
queryNoText to search for in names, descriptions and tags.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "utilities",
      -  "productivity",
      -  "developer",
      -  "education",
      -  "sports",
      -  "environment",
      -  "ai-agents"
      -]New value: +[
      +  "ai-agents",
      +  "developer",
      +  "design-media",
      +  "productivity",
      +  "business",
      +  "finance",
      +  "games",
      +  "education",
      +  "health",
      +  "utilities"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one real trait — only published entries are returned — but says nothing about pagination behavior (despite a 'page' param), result ordering, or typical result volume.

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?

Two short sentences with no filler, and the primary purpose is front-loaded. It is arguably too terse given the gaps, but nothing present is wasteful.

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

Completeness2/5

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

A 4-parameter search tool with no annotations and no output schema needs the description to cover pagination and result shape. It covers neither, leaving the agent unable to page through results or anticipate returned fields confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 25%, with only 'query' documented. The description adds no meaning for 'tag', 'page', or 'category'; 'page' in particular is left unexplained, so an agent cannot tell whether it is 1-indexed, how many results per page, or how to detect the last page.

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 ('Search the PostLaunchKit directory of reviewed free tools and projects') plus a scope qualifier ('Returns published entries only'). It is distinguishable from get_project and list_categories by the verb 'search', though it never names those siblings explicitly.

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 by the verb 'search' — there is no statement of when to prefer this over get_project (single lookup) or list_categories (browsing facets). The 'published entries only' note is a scope constraint rather than routing guidance.

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