Skip to main content
Glama

Mike Reams: architecture writing, diagrams and toolbox

List the agent skills

list_skills
Read-onlyIdempotent

List the skills in the AI Library, filtered by origin, category or keyword. An original (written by Mike) comes with its install command; a curated one (someone else's work that he reviewed) with its author and source. Each has a page with the details.

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
queryNoKeyword in the name, summary, outcome or author
originNoWritten by Mike, or reviewed by him
categoryNoCategory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "Enterprise architecture",
      -  "Review & QA",
      -  "Diagrams",
      -  "Frontend",
      -  "Design systems",
      -  "Debugging",
      -  "Planning",
      -  "Security"
      -]New value: +[
      +  "Enterprise architecture",
      +  "Review & QA",
      +  "Security",
      +  "Diagrams",
      +  "Frontend",
      +  "Design systems",
      +  "Debugging",
      +  "Planning"
      +]
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety profile needs no restating. The description does add useful shape about results: originals carry an install command, curated entries carry author and source. It says nothing about result ordering, volume, or whether unfiltered calls return everything, which leaves real gaps for a list endpoint.

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 tight sentences, front-loaded with purpose and filtering scope, followed by the result-shape distinction and the pointer to detail pages. No filler and no repetition of schema 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?

No output schema exists, yet the description compensates by describing what records contain and how the two origin types differ. With three optional, fully documented, enum-constrained parameters, the definition is nearly complete; only pagination and default-result behavior are unaddressed.

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% with enums and descriptions for all three parameters, so the baseline is 3. The description goes slightly beyond by explaining what the origin values mean in practice (original = written by Mike and ships with an install command; curated = reviewed third-party work with author and source), which clarifies the enum semantics rather than merely restating them.

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 skills in the AI Library") plus the dimensions available for narrowing (origin, category, keyword). An agent can immediately distinguish this from list_diagrams or list_toolbox based on resource alone.

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?

Filter conditions are implied by "filtered by origin, category or keyword," and the closing sentence "Each has a page with the details" hints that get_page is the follow-up for detail. There is no explicit when-to-use/when-not statement, and no mention of how this differs from search_site for keyword lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources