Skip to main content
Glama

SkillU

search_skills

Search SkillU's catalog of curated Agent Skills by keyword, with optional category and tier filters. Returns matching skills with their name, tagline, category, tier and detail-page URL. Use an empty query to list skills (picks are ordered as in the catalog).

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

Input Schema

NameRequiredDescriptionDefault
tierNoFilter by tier.
limitNoMax results to return (default 10, max 20).
queryNoKeyword to match against skill name, tagline, description and category. Empty means list all.
categoryNoFilter by category, e.g. automation, 3d, image, video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the returned fields and the ordering behavior for empty queries, which is real value, but says nothing about how keyword matches are ranked, whether matching is fuzzy or exact, or any rate/call 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?

Three tight sentences with the core action and scope front-loaded, and the empty-query rule placed last where it reads as a usage note. Nothing is redundant, though the return-field sentence overlaps slightly with what calling the tool reveals.

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?

No output schema exists, but the description enumerates the return fields (name, tagline, category, tier, detail-page URL) so the agent knows what it gets back. Combined with the empty-query listing mode and the limit cap in the schema, it is nearly complete for a simple search tool; only match-ranking semantics are missing.

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 all four parameters including the enum tier and the limit default/max are already documented in the schema. The description restates the filters (keyword, category, tier) without adding format, matching, or syntax detail beyond the schema.

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 and resource ("Search SkillU's catalog of curated Agent Skills") plus what narrows the search (keyword, category, tier). It also names the return fields, so an agent can distinguish it from get_skill (single detail page) and list_categories without opening the schema.

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 explicit guidance for the empty-query case ("Use an empty query to list skills") and notes catalog ordering for that mode. It does not name alternatives or state when-not to use it, so it falls short of the top tier.

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