Skip to main content
Glama

Search Installed Skills

search_installed_skills

Search installed skills by relevance to find matching skill metadata and scores without loading skill content. Use stack or task keywords to locate the right skill before loading it.

Instructions

Busca skills instaladas por relevância e devolve só metadados resumidos + score.

Não carrega nenhum SKILL.md. Use palavras-chave da stack/tarefa (os metadados costumam estar em inglês) e faça mais de uma busca se a tarefa cruzar domínios.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description still discloses the key behavioral trait: this is a metadata-only discovery step that does not load SKILL.md files, and results are relevance-ranked with scores attached. Read-only nature is strongly implied by "Busca", though no explicit statement about side effects or failure behavior is given.

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 purpose, then the critical constraint, then the query advice. No filler or restatement of the tool name; every sentence earns its place.

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?

The tool is simple (2 params, flat schema, output schema present so return values need no explanation), and the description covers purpose, differentiation, and query strategy. The only material gap is the undocumented `limit` parameter, which caps completeness at a 4.

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 0%, so the description must carry parameter meaning. It does this well for `query` (keyword style, English metadata, multiple searches for cross-domain tasks) but never mentions `limit`, leaving one of two parameters entirely undocumented.

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 ("Busca skills instaladas por relevância") and exactly what comes back ("só metadados resumidos + score"). The line "Não carrega nenhum SKILL.md" cleanly separates it from a content-fetching sibling such as get_skill_content, so an agent can pick the right tool without opening either 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 concrete when-and-how guidance: use stack/task keywords, note that metadata is usually in English, and run more than one search when the task spans domains. It stops short of explicitly naming the follow-up tool to load full content, leaving the exclusion implied rather than stated.

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