Skip to main content
Glama

Read skill reference resource

read_skill_resource
Read-only

Reads a bundled reference or template file from a production skill so agents can load the exact guidance or asset needed before generating output.

Instructions

Read a bundled reference or template file (e.g. "references/..." or "templates/...") belonging to a production skill.

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": {
      "resource": "<resource>"
    },
    "name": "read_skill_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesRelative path of the resource inside the skill.
skill_idNoSkill ID that owns the resource.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.7/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 file is bundled inside a skill, reinforcing the confined scope, but says nothing about failure behavior for missing resources, path constraints, or file size limits.

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 front-loaded sentence that identifies the verb, the artifact type, the path forms, and the owning skill. Nothing is redundant and nothing is buried.

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 two-parameter, fully documented read tool with no output schema, the description covers what is being read and where it lives. It could do slightly more by noting that the return value is the file's contents or how sibling skill-loading tools relate, but the essential call information is present.

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 real value by illustrating the expected shape of the 'resource' parameter with concrete path examples ('references/...', 'templates/...') that the schema's 'Relative path' wording does not convey. The skill_id ownership is likewise reinforced ('owns the resource').

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?

States a specific verb ('Read') and resource ('bundled reference or template file'), and the example path prefixes ('references/...', 'templates/...') pin down exactly what kind of artifact this returns. It distinguishes itself from load_skill only implicitly through the word 'bundled' and the required skill_id, not by naming the sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'belonging to a production skill' implies the tool is used after a skill is known/loaded, and the required skill_id reinforces that ordering. However, it never says when to reach for this instead of load_skill or search_skills, and gives no preconditions, so usage is inferred rather than stated.

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