Skip to main content
Glama

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

Leer una skill

get_skill
Read-only

Devuelve el prompt completo de una skill de ia-skills.com a partir de su slug (lo da search_skills).

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": {
      "slug": "<slug>"
    },
    "name": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is covered. The description adds that the payload is the complete prompt rather than metadata or a summary, which is useful, but it says nothing about behavior on an invalid/unknown slug, response size, or authentication against ia-skills.com. With annotations present the bar is lower, so a 3 fits.

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?

One sentence, zero filler, and the essential information (return value, input, provenance of the input) is front-loaded. Nothing repeats the title or name.

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?

For a one-parameter read tool with no output schema, the description covers what the tool does, what it returns, and where the key comes from. The only meaningful gap is the absence of failure behavior for a nonexistent slug, which is minor for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the single 'slug' property has no description — so the description must compensate, and it does: it explains that slug is the skill identifier and that it originates from search_skills. It stops short of stating format or validation rules for the slug, which keeps it below a 5.

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 states a specific verb and resource ('Devuelve el prompt completo de una skill') plus the addressing key ('a partir de su slug'), so an agent knows exactly what comes back. It also anchors itself against the sibling by noting the slug is the one given by search_skills, making the two tools distinguishable 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?

The parenthetical '(lo da search_skills)' tells the agent the intended flow: locate a skill with search_skills first, then fetch it here. There are no explicit when-not conditions (e.g., what to do if the slug is unknown), but the usage context is clear rather than merely implied.

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.