Tenarius Wiki MCP

get_adventurer_profile

Access your locally configured adventurer profile to tailor builds, farming strategies, and player objectives. Your data stays on your machine and is never sent online.

Instructions

Lee el perfil del aventurero configurado localmente en esta máquina.

Datos 100% locales (~/.config/tenarius-wiki-mcp/). No se envían a internet. Usar para personalizar builds, farming y objetivos del jugador.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_adventurer_profile"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries full responsibility. It discloses that data is '100% locales' and the exact path (~/.config/tenarius-wiki-mcp/), and explicitly states 'No se envían a internet' (not sent to the internet). This provides a strong privacy/behavioral profile, though it doesn't detail the return structure or potential side effects.

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 three short, front-loaded sentences. The main action is stated first, followed by essential privacy and usage details. No redundant words.

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

Completeness5/5

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

For a 0-parameter tool with an output schema, this description is complete. It covers what the tool does, why to use it, where data comes from, and privacy implications. No missing critical information.

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

Parameters4/5

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

The tool has 0 parameters, so the baseline is 4. The description doesn't need to explain parameters, and the schema already reflects this. No additional parameter information is necessary.

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 'Lee el perfil del aventurero configurado localmente' (reads the locally configured adventurer profile), using a specific verb and resource. This distinguishes it from the sibling wiki/reference search tools, which focus on external content rather than the local profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage context: 'Usar para personalizar builds, farming y objetivos del jugador' (use to customize builds, farming, and player goals). It does not list exclusions or alternative tools, but the purpose is clear enough that the agent can infer when to use it.

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

Deploy Server