List skill sets
list_setsList curated skill sets (bundles) with their skill slugs.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Marketing Skills Directory
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only says it lists sets with skill slugs, missing behavioral details like read-only nature, auth requirements, 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.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, 8 words. Very concise but earns its place. Could add more context without being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a parameterless list tool but missing details about scope (all sets? filtered?), output format, or whether it returns all sets.
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 has zero parameters with 100% coverage, so baseline is 4. Description adds context that output includes skill slugs, which is not in schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states it lists curated skill sets (bundles) with their skill slugs, which is a specific verb+resource and distinguishes from siblings like list_skills or get_set.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives (e.g., get_set for a single set). No context about use cases or limitations.
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.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool serves a distinct purpose: retrieving sets, skills, categories, sets list, skill list, recommendation, and search. No overlapping functionality.
Naming Consistency5/5
All tools use consistent snake_case with verb_noun pattern (e.g., get_set, list_categories, search_skills). No mixing of styles.
Tool Count5/5
Seven tools is well-scoped for a skills directory, covering browsing, search, recommendation, and detailed retrieval without overburdening the agent.
Completeness4/5
Covers core operations: listing categories, skills, sets; searching; recommending; retrieving details. Minor gap: no direct category detail tool, but list_categories provides counts.