Skip to main content
Glama

ia-skills: prompts y skills de IA en español

Buscar skills

search_skills
Read-only

Busca prompts y skills de IA en español en el catálogo de ia-skills.com, ordenados por popularidad. Úsala cuando el usuario quiera un prompt o skill para una tarea profesional (marketing, desarrollo, legal, ventas, RRHH, finanzas...).

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
limitNo
queryYesQué se busca, en español. Ej: "revisar contratos", "cold email B2B".
professionNoSlug de profesión para acotar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior — the results come from the ia-skills.com catalog and are ranked by popularity — but says nothing about how many results come back, whether the catalog is exhaustive, or what identifiers a result carries.

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?

Two tight sentences: the first establishes what and where, the second establishes when. No filler, and the scope statement is front-loaded ahead of the usage cue.

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 no output schema, the description covers the what/where/when and ranking, but omits what a result looks like — notably whether it returns a slug or id that the sibling get_skill expects. That handoff detail matters for an agent chaining search into retrieval.

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 67% and both documented parameters already explain themselves, including the Spanish-language requirement for query and the profession slug enum. The description reinforces that content is in Spanish but adds no new meaning about limit, defaults, or how profession narrows 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?

Names a specific verb ("Busca") and resource ("prompts y skills de IA") plus the source catalog and the ordering rule (popularidad), so the agent knows exactly what the tool returns. It never mentions the sibling get_skill, so the distinction between searching the catalog and fetching one skill is left implicit.

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?

"Úsala cuando el usuario quiera un prompt o skill para una tarea profesional" gives a clear triggering condition and enumerates domains (marketing, desarrollo, legal, ventas, RRHH, finanzas). It stops short of exclusions or naming an alternative for the single-item case.

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.