Get skill set
get_setReturn a skill set with full details for each contained skill.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Set slug, e.g. "video-production-suite". |
Marketing Skills Directory
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must cover behavior. It only says 'return' without discussing side effects, permissions, or data scope. Inadequate for a non-annotated tool.
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?
Single sentence with no filler. Front-loaded purpose.
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?
No output schema, so description should hint at return structure. 'Full details' is vague; could specify what details are included.
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 covers 100% of parameter meaning (slug with example). Description adds no extra semantics beyond schema, meeting baseline.
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?
The description clearly states it returns a skill set with full details for each skill, distinguishing it from siblings like get_skill or list_sets.
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?
Usage is implied but no explicit guidance on when to use or alternatives. Agent might infer from context but lacks clear direction.
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.