Skip to main content
Glama
bshea-1

Routed

by bshea-1
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

list_skills

Find and filter locally indexed agent skills using optional substring search across names, descriptions, and tags, or restrict by host environment.

Instructions

List and filter all locally indexed agent skills from SQLite. Behavior: Read-only, sub-millisecond query with zero side effects. Usage Guidelines: Use to browse available skills without a prompt. Use scan_skills to refresh index after adding or editing skill files, route_skill to match prompts, or get_skill for specific skill instructions. Parameters: filter (substring search) and host (tool environment) combine as an AND filter. Returns all skills when omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoOptional host environment filter to restrict results to a specific tool (e.g. cursor, antigravity, claude-code, gemini-cli, hermes, codegate, openclaw, openmanus, lmstudio, ollama).
filterNoOptional substring query matched case-insensitively across skill names, descriptions, and tags.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / filter / description
      Previous value: -"Optional substring filter matched case-insensitively against skill names, descriptions, and tags."New value: +"Optional substring query matched case-insensitively across skill names, descriptions, and tags."
    • changedInput schema / properties / host / description
      Previous value: -"Optional host environment filter to limit results to a specific tool (e.g. cursor, antigravity, claude-code, gemini-cli, hermes, codegate, openclaw, openmanus, lmstudio, ollama)."New value: +"Optional host environment filter to restrict results to a specific tool (e.g. cursor, antigravity, claude-code, gemini-cli, hermes, codegate, openclaw, openmanus, lmstudio, ollama)."
  2. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / filter / description
      Previous value: -"Optional filter query across names, descriptions, and tags."New value: +"Optional substring filter matched case-insensitively against skill names, descriptions, and tags."
    • changedInput schema / properties / host / description
      Previous value: -"Optional host environment filter."New value: +"Optional host environment filter to limit results to a specific tool (e.g. cursor, antigravity, claude-code, gemini-cli, hermes, codegate, openclaw, openmanus, lmstudio, ollama)."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries full responsibility. It clearly states 'Read-only, sub-millisecond query with zero side effects,' which fully discloses behavioral characteristics with no contradictions.

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?

Organized into clear sections (Behavior, Usage Guidelines, Parameters) with no redundant wording. Every sentence adds meaningful information, achieving high density without bloat.

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?

The tool is simple (list/filter, no output schema needed). The description covers purpose, behavior, usage, parameter semantics, and alternatives comprehensively, leaving no relevant gaps for an agent to invoke it correctly.

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 description coverage is 100% so baseline is 3, but the description adds valuable context: 'combine as an AND filter' and 'Returns all skills when omitted,' which clarifies parameter interaction and default behavior beyond the individual schema descriptions.

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 ('list' and 'filter') with a clear resource ('locally indexed agent skills from SQLite'). Explicitly differentiates from siblings by naming alternative tools and their purposes (scan_skills, route_skill, get_skill).

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?

Provides explicit when-to-use guidance ('Use to browse available skills without a prompt') and explicitly names alternatives with their appropriate contexts, leaving no ambiguity about selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bshea-1/Routed'

If you have feedback or need assistance with the MCP directory API, please join our Discord server