Skip to main content
Glama
Sign In
cc-recommender

cc-recommender

by yuji0809
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

キーワード検索

search_skills

Find relevant Claude Code plugins, MCP servers, skills, workflows, hooks, commands, and agents by keyword, with optional type filters to narrow results.

Instructions

キーワードですべてのタイプ（プラグイン、MCPサーバー、スキル、ワークフロー、フック、コマンド、エージェント）を検索します。デフォルトではすべてのタイプを検索します。ユーザーが特定のタイプのみを要求した場合のみ types パラメータで絞り込んでください。

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

Input Schema

NameRequiredDescriptionDefault
queryYes検索キーワード
typesNoフィルタするタイプ。指定しない場合はすべてのタイプを検索します。ユーザーが特定のタイプを明示的に要求した場合のみ指定してください。
max_resultsNo最大結果数

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden, and it does disclose the default behavior of searching across all types. It does not mention result ranking, truncation, pagination, or the fact that max_results is capped, so the behavioral picture is partially but not fully filled in.

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?

Three short sentences, front-loaded with the scope statement followed by the default and the narrowing rule. Every sentence contributes and nothing is redundant.

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

Completeness3/5

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

For a simple read-only search with a fully documented schema and no output schema, the description covers the essentials. It still omits what the results look like and how the result cap interacts with max_results, which an agent would benefit from knowing.

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 schema already documents 'types' with identical default-and-only-when-requested wording. The description largely restates what the schema provides and adds no new syntax, format, or interaction details for query or max_results.

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 gives a specific verb (search) and resource (all types: plugins, MCP servers, skills, workflows, hooks, commands, agents) with an explicit default scope. It is clear what the tool does, but it never mentions the sibling tools (get_skill_details, recommend_skills, list_categories), so the distinction from them is left to inference.

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?

There is useful guidance on when to use the types filter ('only narrow down when the user requests a specific type only'), which is real usage advice. However, there is no guidance on when to use this tool versus recommend_skills or list_categories, and no exclusions or prerequisites are stated.

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