Skip to main content
Glama
olaservo

Skill Jack MCP

by olaservo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read Skill File

skill-resource
Read-onlyIdempotent

Read files referenced by skill instructions, such as scripts, snippets, and templates. Pass a directory path to read all files at once; binary files return as base64 resources.

Instructions

Read files referenced by skill instructions (scripts, snippets, templates). Use when skill instructions mention specific files to read or copy. Pass a directory path (e.g., 'templates') to read all files in that directory at once. Text files are returned as text; a binary file is returned as an embedded base64 resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative path to file or directory. Examples: 'snippets/tool.ts' (single file), 'templates' (all files in directory), '' (list available files).
skillYesSkill name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / path / description
      Previous value: -"Relative path (e.g., 'snippets/tool.ts'). Empty string lists all files."New value: +"Relative path to file or directory. Examples: 'snippets/tool.ts' (single file), 'templates' (all files in directory), '' (list available files)."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior. The description adds important context beyond annotations: directory paths read all files at once, text is returned as text, and binary is returned as embedded base64. It still leaves error or partial-read behavior unstated.

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?

Four sentences, each front-loaded and purposeful: purpose, usage trigger, directory behavior, and return format. No redundant or filler content.

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?

With no output schema, the description usefully explains return formats for text and binary files. It omits some edge cases, such as the empty-path listing behavior, but that is already covered in the schema, so the definition is largely complete for an agent to call it correctly.

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 100%, so the schema already documents both required parameters, including path examples and the empty-path listing behavior. The description's statement about directory paths adds little beyond what the schema already provides, so the baseline of 3 applies.

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 (files referenced by skill instructions) with examples of file types. It is clear enough to distinguish from skill-config and skill-display siblings, but it never explicitly names or contrasts with the closest sibling, load-skill.

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?

Gives a concrete trigger: 'Use when skill instructions mention specific files to read or copy.' It also explains the directory-path case, but offers no when-not guidance or sibling alternatives.

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

Deploy Server

Other Tools