Skip to main content
Glama
Sign In
Agent Genesis Tools

Agent Genesis Tools

by xvacorx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_vault_skills

Search and filter offline vault skills by keyword or category to discover capabilities before installation; returns matching skill names, categories, and summaries.

Instructions

Searches and enumerates specialized skills from the offline vault (915+ skills) by keyword or category. Safe, read-only operation: reads local catalog.json with zero side effects, no mutations, and no network access. When query and category are both provided, applies a logical AND filter. When both are omitted or empty, returns the top general engineering skills up to the specified limit. If no skills match, returns a helpful message with suggested search keywords.

When to use: Call to discover skill names and capabilities before installation. When NOT to use: Do not use to install or execute skills; call equip_skill once a specific skill name is chosen. Returns: Formatted list of matching skills containing name, category tag, and summary description, plus remaining match count.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of skill entries to return in a single call (integer from 1 to 50). Defaults to 12 to conserve context tokens.
queryNoSearch term matched case-insensitively against skill names, folder paths, and descriptions (e.g. 'react', 'unity', 'docker', 'shader', 'kubernetes'). Empty string matches all skills.
categoryNoDomain filter. Allowed values: 'gamedev', 'devops', 'frontend', 'security', 'ai', 'general', 'database', 'testing'. Combined with query using logical AND. Empty string searches across all categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.2
    • changedInput schema / properties / category / description
      Previous value: -"Optional domain category filter. Allowed values: 'gamedev', 'devops', 'frontend', 'security', 'ai', 'general', 'database', 'testing'. If omitted, searches across all categories."New value: +"Domain filter. Allowed values: 'gamedev', 'devops', 'frontend', 'security', 'ai', 'general', 'database', 'testing'. Combined with query using logical AND. Empty string searches across all categories."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of skill results to return (integer between 1 and 50). Defaults to 12 to preserve prompt tokens."New value: +"Maximum number of skill entries to return in a single call (integer from 1 to 50). Defaults to 12 to conserve context tokens."
    • changedInput schema / properties / query / description
      Previous value: -"Search term or keyword to match against skill names and descriptions (e.g. 'kubernetes', 'react', 'shader', 'unity', 'security', 'docker'). If empty, returns skills within the specified category or top general skills."New value: +"Search term matched case-insensitively against skill names, folder paths, and descriptions (e.g. 'react', 'unity', 'docker', 'shader', 'kubernetes'). Empty string matches all skills."
  2. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category (e.g. 'gamedev', 'devops', 'frontend', 'security', 'ai', 'general')"New value: +"Optional domain category filter. Allowed values: 'gamedev', 'devops', 'frontend', 'security', 'ai', 'general', 'database', 'testing'. If omitted, searches across all categories."
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default: 12)"New value: +"Maximum number of skill results to return (integer between 1 and 50). Defaults to 12 to preserve prompt tokens."
    • changedInput schema / properties / query / description
      Previous value: -"Search keyword (e.g. 'kubernetes', 'react', 'shader', 'unity', 'security', 'docker')"New value: +"Search term or keyword to match against skill names and descriptions (e.g. 'kubernetes', 'react', 'shader', 'unity', 'security', 'docker'). If empty, returns skills within the specified category or top general skills."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that it reads a local catalog.json, that it has zero side effects, no mutations and no network access, and it explains the AND semantics of combining filters, the fallback behavior when both filters are empty, and the no-match path. It also documents the return shape and the remaining-match count, which is behavior an agent needs to decide follow-up calls.

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?

Well front-loaded and cleanly segmented into purpose, safety, filter semantics, when/when-not, and returns. Slight redundancy in the safety clause ('zero side effects, no mutations, and no network access' are near-synonyms) keeps it just short of a 5.

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 three-parameter, zero-required, read-only lookup tool with no annotations and no output schema, the description covers everything an agent needs: default behavior, filter combination rules, empty-result handling, return contents, and the handoff to equip_skill. The absence of an output schema is compensated by the explicit 'Returns:' sentence.

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 baseline is 3, but the description adds meaning beyond the schema: the both-omitted/both-empty case returns top general engineering skills up to the limit, and the AND combination is restated at the behavioral level. It does not add matching-syntax detail (e.g. stemming or multi-word phrase handling) beyond the schema's case-insensitive note, which keeps it at 4 rather than 5.

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 pair ('searches and enumerates') with the exact resource ('specialized skills from the offline vault') and a concrete scale cue (915+ skills) plus the search axes (keyword or category). The final line explicitly separates it from equip_skill, so an agent can distinguish it from the sibling without opening a schema.

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 an explicit 'When to use' (discover names and capabilities before installation) and an explicit 'When NOT to use' naming the alternative (don't install or execute; call equip_skill once a name is chosen). The two-step discovery-then-act workflow is spelled out rather than inferred.

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

Deploy Server

Other Tools