Skip to main content
Glama

skill_read

Read a skill file from ./skills-repos using a partial relative path, and optionally filter lines with a regex to focus output.

Instructions

Read a file from ./skills-repos by (partial) relative path, optionally filtering lines with a regex.

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": {
      "target": "<target>"
    },
    "name": "skill_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
grepNo
targetYesRelative path or distinctive fragment, e.g. 'leanrea', 'apk-reverse', 'MASTER-ROUTING.md'
max_linesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only conveys that this is a read with optional regex filtering. It does not disclose what happens when a partial path matches multiple files (ambiguous resolution), whether truncation occurs, or how max_lines default of 200 affects results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler and the scope stated before the optional behavior. Slightly dense with the parenthetical '(partial)', but nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter path-resolution tool with no annotations and no output schema, key behavior is missing: ambiguous partial-match resolution, truncation/line-limit behavior, and what the returned content looks like when grep filters lines.

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

Parameters2/5

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

Schema coverage is only 33%, so the description should compensate; it does explain 'grep' as a regex line filter, but says nothing about 'max_lines' beyond its bare numeric default, and gives no detail on match semantics for the partial 'target' beyond the schema example.

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?

Names a specific verb ('Read') and resource ('a file from ./skills-repos') and scopes it to relative-path lookup with optional regex line filtering. It is distinguishable from a listing tool, though it never names skill_list as the alternative.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no exclusions or prerequisites. The only implied usage is that this retrieves skill file content rather than enumerating it; an agent must infer the read-vs-list split from sibling names alone.

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