list_latest_articles
List the newest public canonical Wikivibe articles.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| locale | No | ru |
Wikivibe MCP
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose all behavioral traits. It only says 'list newest public canonical articles,' omitting details like ordering (assumed by date), pagination behavior (limited by max 10), rate limits, or authentication needs. This is insufficient for full 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 a single concise sentence with immediate clarity on the main action. However, it sacrifices necessary details like parameter explanations, making it only adequate in structure.
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 tool's simplicity (2 parameters, no output schema), the description could be complete with a few extra sentences on parameters and usage. As is, it leaves gaps: what are 'canonical' articles? What is the output format? This hampers autonomous selection and invocation.
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%, and the description does not mention the 'limit' or 'locale' parameters. It does not explain that limit controls the number of articles returned or that locale filters by language. The agent must infer from default values and enum, which is inadequate.
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 tool lists the newest public canonical articles. The verb 'List' and resource 'newest public canonical Wikivibe articles' are specific and distinguish it from siblings like get_article (single) or search_articles (search).
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?
The description implies usage for retrieving recent articles but does not explicitly state when to use this tool versus alternatives like search_articles. No exclusions or when-not guidance is provided, though the context is clear.
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.