Skip to main content
Glama
Sign In

Agent Wikis

by io.github.tonbistudio
OverviewDiscussionsAdmin

List skills

list_skills
Read-onlyIdempotent

List the agent skills library: field-tested procedures for specific jobs (e.g. benchmarking a local model, building a browser game, producing a video). Each entry has name, one-line description (when to use it), access ("free" or "pro"), readable (whether YOU can read it with your current access), the backing wiki if any, and file count. Pass query to filter by keywords. Then read_skill a matching skill and follow it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keywords; every term must appear in the name, description or backing wiki.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (access free/pro, `readable` relative to YOUR current access, backing wiki, file count), which is significant since there is no output schema. It does not cover volume limits or pagination.

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?

Three compact sentences: identity, contents, then action. The field enumeration is dense but earns its space because no output schema exists. Nothing is redundant with the title or annotations.

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?

For a one-parameter, read-only listing tool with no output schema, the description covers purpose, return shape, filtering, and the follow-up workflow. An agent can select and invoke it with no open questions about how to use the result.

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 coverage is 100% and the schema's own `query` description ('every term must appear in the name, description or backing wiki') is actually more precise than the description's 'filter by keywords.' The description adds no syntax, matching, or empty-result behavior beyond the schema, so the baseline of 3 applies.

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 ('List the agent skills library') and immediately characterizes the content as 'field-tested procedures for specific jobs' with three concrete examples. This distinguishes it cleanly from read_skill, which the description explicitly names as the follow-up action.

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 clear when-to-use context (browsing the skills library) and an explicit next step: 'read_skill a matching skill and follow it.' It also explains when to pass `query`. It stops short of stating exclusions or contrasting with sibling listers like list_agent_tools or list_wikis, so full marks are not warranted.

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