Skip to main content
Glama

Read one section of a skill

skill_section
Read-only

Retrieve one heading section of a skill's SKILL.md instead of the whole file. Omit the heading to get the outline with line numbers first.

Instructions

Return one heading-section of a skill's SKILL.md instead of the whole file. Omit heading to get the outline (headings with line numbers) first.

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": "<skill>"
    },
    "name": "skill_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYesSkill id or name
headingNoHeading text (exact or partial); omit for the outline

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With only readOnlyHint=true supplied, the description adds useful behavior: the tool returns a bounded slice rather than the entire file, and the outline form includes headings with line numbers. It still doesn't say whether a partial heading match can return multiple sections or whether a non-match errors, which matters for a read tool whose output isn't schematized.

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?

Two sentences, front-loaded with what is returned, with the outline workflow immediately after. Every clause carries information and nothing is redundant.

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 two-parameter read tool with full schema coverage and no output schema, the description covers input modes well but leaves the returned payload underspecified — it's unclear whether the section comes back as raw markdown, whether the heading is included, and how line numbers are formatted. Adequate but with a clear gap on return shape.

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 100%, so the baseline is 3, but the description adds value by framing 'omit heading' as an intentional mode (outline) rather than a missing value, and it discloses that the outline carries line numbers. This goes slightly beyond the schema's terse 'omit for the outline' phrasing.

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 states a specific verb and resource ('Return one heading-section of a skill's SKILL.md') and contrasts it with the alternative behavior of reading the whole file. The scope is clear enough that an agent knows this is a scoped-read tool, though no sibling is named to anchor the distinction.

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 gives a concrete two-step workflow: omit the heading first to see the outline, then request a section. That is genuine usage context, not merely implied. It doesn't cover failure cases (e.g., what to do when a heading doesn't match), so it stops short of a full when/when-not treatment.

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