Skip to main content
Glama
Sign In
mcp-easy-installer

mcp-easy-installer

by onigetoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_mcp_server

Search GitHub for MCP servers by specifying a query to locate repositories for integration with AI tools.

Instructions

Search for MCP servers on GitHub. Uses GITHUB_TOKEN from server config.

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_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query for GitHub repositories (e.g. "mcp-server", "language:typescript mcp")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. Only mentions token usage; lacks details about rate limits, pagination, result format, or any side effects.

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 sentences, front-loaded with purpose, no wasted words.

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?

Simple tool with one parameter and no output schema; description is mostly complete but could mention the nature of the return value (e.g., list of repositories).

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% with a clear description of the 'query' parameter. Tool description adds no extra semantic value beyond the parameter's schema definition.

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?

Description clearly states it searches for MCP servers on GitHub using a specific verb+resource. Distinguishes from sibling tools (repair, install, uninstall) which are different actions.

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?

Implied usage as a search tool vs siblings is clear, but no explicit when-to-use or when-not-to-use guidance beyond mentioning the GITHUB_TOKEN dependency.

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