Skip to main content
Glama
Sign In
skill-ninja-mcp-server

skill-ninja-mcp-server

by aktsmm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

skillNinja_webSearch

Search GitHub for SKILL.md files to find and discover reusable AI agent skills.

Instructions

Search for Agent Skills on GitHub. Finds SKILL.md files across GitHub repositories. / GitHub でスキルを検索

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query for GitHub

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, and the description fails to disclose important behavioral traits like rate limits, authentication needs, or what happens if no results are found. It only mentions the action without side effects or constraints.

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 short and to the point, but it includes redundant phrasing ('Search for Agent Skills on GitHub' and 'Finds SKILL.md files across GitHub repositories' are similar). Could be more concise.

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?

Given the lack of output schema and only one parameter, the description is incomplete. It does not explain the return format (e.g., list of repositories, contents of SKILL.md) or any result handling, leaving the agent uncertain about the tool's full usage.

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% and the parameter 'query' already has a clear description. The tool description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states it searches for Agent Skills on GitHub and specifically finds SKILL.md files, distinguishing it from sibling tools like skillNinja_search which likely searches locally or differently.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as skillNinja_search or skillNinja_recommend. The description only states what it does, not when to use it.

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