Skip to main content
Glama

Get Skill Content

get_skill_content

Loads the complete SKILL.md for one selected skill after search, so AI clients can retrieve only the chosen skill's instructions on demand.

Instructions

Lê o SKILL.md completo de UMA skill escolhida (use após search_installed_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": {
      "skill_name": "<skill_name>"
    },
    "name": "get_skill_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so behavioral disclosure rests on the description, and 'Lê' (reads) at least makes the read-only nature clear. Beyond that it is silent on what happens with an unknown skill name, whether content is truncated for large SKILL.md files, or authentication requirements — notable gaps for a zero-annotation tool.

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?

A single sentence with zero filler, front-loaded on the action and resource, with the prerequisite tucked into a parenthetical. Nothing is repeated from the title alone.

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 an output schema covering return values and a single documented prerequisite, the description is adequate to call it correctly. The remaining gap is failure behavior on an unrecognized skill name, which is minor given the tool's simplicity.

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% and the single skill_name parameter is undocumented in the schema, so the description must compensate. It does add that the value must identify one chosen skill, implying it comes from prior search results, but it never states whether matching is exact, case-sensitive, or by path.

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 and resource: it reads the complete SKILL.md of ONE chosen skill. Capitalizing 'UMA' (one) signals a scope boundary against broader search-style tools, though it stops short of naming search_installed_skills as the alternative rather than just a precursor.

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?

It explicitly states the workflow condition 'use after search_installed_skills', so the agent knows the prerequisite step before calling. It gives no when-not guidance or handling for calling it with a skill name that was never searched, which keeps it from a 5.

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