list_sections
List public Wikivibe sections that contain indexable articles.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | ru |
Wikivibe MCP
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It indicates a read-only operation ('List') and specifies that only public sections with indexable articles are returned. However, it does not disclose potential pagination, authentication requirements, or rate limits. This is adequate for a simple list but lacks depth.
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?
The description is a single, front-loaded sentence with no wasted words. However, it could be improved by adding a brief note about the 'locale' parameter without sacrificing conciseness.
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 the lack of output schema, the description should explain what information is returned (e.g., section names, IDs). It also omits the role of the 'locale' parameter. The description is insufficient for a complete understanding, especially with no annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description does not mention the 'locale' parameter at all. The agent receives no semantic help beyond the enum values in the schema, leaving the parameter's purpose completely unexplained.
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 the verb 'List' and the resource 'public Wikivibe sections that contain indexable articles', which distinguishes it from sibling tools like 'list_latest_articles' or 'search_articles'. It is specific and unambiguous.
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 is provided on when to use this tool versus alternative tools such as 'list_latest_articles' or 'search_articles'. There are no conditions, prerequisites, or exclusions mentioned.
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.6/5.0
Disambiguation5/5
Each tool targets a distinct resource and action: get for single items, list for collections, search for finding, and recommend for project-based suggestions. No two tools have overlapping purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_article, search_skills). The verbs and nouns are clearly descriptive and uniform across the set.
Tool Count5/5
With 9 tools, the set is well-scoped for a public knowledge server covering articles, design templates, and AI skills. Each tool serves a clear role without redundancy or overload.
Completeness4/5
The tool set provides comprehensive read and search operations for all three content types, plus a recommendation feature. Minor gaps exist, such as no listing of all articles by section or pagination support, but core workflows are covered.