List / browse skills
list_skillsBrowse the catalog, optionally filtered by category. Paginated.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| category | No | Filter by category name (see list_categories). |
Marketing Skills Directory
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must convey behavior. It mentions pagination indirectly via 'limit' and 'offset', but does not disclose ordering, response structure, or effects. Minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (one sentence), which is concise but lacks important details like return values and pagination clues. It is not front-loaded with critical info.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and only 33% parameter description coverage, the description fails to specify return structure or pagination behavior. It is incomplete for a tool with 3 parameters and optional filtering.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 33% (category described). The description adds no detail beyond the schema for 'limit' and 'offset', and 'category' is only repeated. Does not compensate for low coverage.
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 clearly states the tool's purpose: browsing the skills catalog with optional category filtering and pagination. It distinguishes from siblings like 'list_categories' (lists categories) and 'search_skills' (likely search).
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 explicit guidance on when to use this tool versus alternatives. The mention of 'optionally filtered by category' implies usage, but no when-not or context for pagination.
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.