Skip to main content
Glama
Sign In

KitScout

by dev.kitscout
OverviewDiscussionsAdmin

search_tools

Read-only

Search ~84k AI agent tools (MCP servers, Agent Skills, Claude Code plugins) by keywords. Returns ranked matches with type, category, GitHub stars, badges (first_party = made by the product's own maker, verified_publisher, live, free_to_try), install line and KitScout page. Use short keywords: product + action, e.g. 'postgres', 'slack post message', 'pdf extract tables'.

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": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this kind of tool
limitNoMax results (default 10)
queryYesKeywords (product names and actions work best)
only_liveNoOnly remote MCP servers that answered our latest daily check
only_officialNoDeprecated alias of only_verified
only_verifiedNoOnly verified publishers (domain-verified registry namespace, Anthropic marketplace). Does not mean made by the product's vendor; see the first_party badge
only_free_to_tryNoOnly remote MCP servers that worked without an API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds real value beyond that: ranked matches, the fields returned (type, category, stars, badges, install line, page), and a glossary of what each badge means (first_party, verified_publisher, live, free_to_try). It is silent on result counts/pagination and empty-result behavior.

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 sentences, front-loaded with scope then usage guidance, with zero filler. The badge parenthetical is dense but each item carries information an agent would otherwise have to guess.

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?

With no output schema, the description appropriately describes what a result contains. For a seven-parameter search tool it is nearly complete; ranking criteria and no-match behavior are the remaining gaps.

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%, so every parameter is already documented, including the only_verified vs first_party distinction and the deprecated only_official alias. The description only reinforces the query format, which is already implied by the schema's 'Keywords (product names and actions work best)'.

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 (search), resource (AI agent tools: MCP servers, Agent Skills, Claude Code plugins) and scope (~84k, keyword-based). An agent can tell this is a discovery/search tool rather than a lookup (get_tool) or taxonomy browse (list_categories).

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?

Gives concrete query-construction guidance: short keywords, product + action, with three examples across different domains. It does not say when to reach for search_tools versus get_tool or list_categories, so routing to siblings is left to inference.

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

All KitScout toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources