Tenarius Wiki MCP

get_wiki_summary

Get a readable summary of a Tenarius RO wiki article by providing its exact title.

Instructions

Resumen legible de un artículo de la Wiki de Tenarius RO.

Args: title: Título exacto (ej. "Set de Equipamiento").

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "get_wiki_summary"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 14, 2026

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'resumen legible' but does not describe error behavior, read-only nature, permissions, or what happens for non-existent titles, leaving significant behavioral aspects undisclosed.

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?

The description is extremely concise, consisting of a single lead sentence and one parameter explanation. Every word contributes value, with the example adding immediate clarity without unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with an output schema, the description covers the core purpose and parameter semantics. It lacks usage guidance and behavioral details, but the presence of an output schema partially compensates for return value documentation. Overall, it is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description enriches the title parameter by stating it must be an exact title and providing a concrete example ('Set de Equipamiento'). This adds meaning far beyond the schema's minimal 'Title' label, fully compensating for the 0% schema description coverage.

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 provides a readable summary of a Tenarius RO Wiki article, using a specific verb ('Resumen') and resource ('artículo de la Wiki'). It distinguishes from sibling tools like get_wiki_page by implying a condensed, human-readable output.

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?

There is no guidance on when to use this tool versus alternatives such as get_wiki_page or search_wiki. The description only states what the tool does, offering no explicit context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server