Skip to main content
Glama
Sign In

Agent Wikis

by io.github.tonbistudio
OverviewDiscussionsAdmin

Read a skill

read_skill
Read-onlyIdempotent

Load one skill to follow it. Without path, returns its SKILL.md (the procedure itself) plus the list of its other files; pass path (e.g. "references/gotchas.md" or "scripts/check.py") to read one of those. If the skill names a backing wiki, use search/read_document on that wiki for current facts while following it. Pro skills need a Pro key; without one you get a preview and how to unlock it.

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

Input Schema

NameRequiredDescriptionDefault
nameYesSkill name from list_skills, e.g. "llm-inference".
pathNoOptional file within the skill, as listed by read_skill. Defaults to SKILL.md.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety needs no restating. The description still adds real context the annotations don't carry: the exact return shape (SKILL.md plus file list), the Pro key requirement, and the preview-with-unlock-path fallback when unauthenticated.

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 front-loaded sentences, each doing distinct work: action, two modes, sibling routing, entitlement behavior. No filler and the primary instruction comes first.

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

Completeness5/5

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

A simple two-parameter read tool with no output schema, yet the description covers return content, defaults, path format, cross-tool routing, and auth gating. Nothing an agent needs to invoke it correctly is missing.

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. The description earns above baseline by giving concrete path examples ("references/gotchas.md", "scripts/check.py") and clarifying that the no-path response additionally returns the list of files, which the schema alone does not state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Load one skill") and immediately defines the two operating modes: no `path` yields SKILL.md plus the file listing, `path` yields one file. This distinguishes it from siblings like read_document and list_skills without needing the schemas.

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

Usage Guidelines5/5

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

Gives an explicit use condition ("to follow it") and routes the agent elsewhere for a different need: search/read_document on the backing wiki for current facts. The name parameter's origin (list_skills) is also documented, so the agent knows the discovery path.

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

All Agent Wikis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources