Skip to main content
Glama
Sign In
prts-mcp

prts-mcp

by 3aKHP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

read_prts_page

Retrieve plain text content of any page from the Arknights PRTS Wiki. Useful for extracting lore, operator profiles, or story scripts.

Instructions

读取 PRTS 维基指定词条的纯文本内容。

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": {
      "page_title": "<page_title>"
    },
    "name": "read_prts_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_titleYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.14
  2. Removedv0.2.13
  3. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It only states output is 'plain text' but omits details like error handling, idempotency, required permissions, or page existence behavior.

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 concise sentence with no wasted words. However, some necessary details are omitted, so it's not perfectly balanced.

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

Completeness3/5

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

Given the tool has one parameter and an output schema, the description is minimally adequate but could be more complete by mentioning what happens on invalid input or additional behavioral aspects.

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 0%, so the description must explain the single parameter 'page_title'. It only vaguely refers to 'specified entry', missing details like exact title format, case sensitivity, or special characters.

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 action 'reads' and the resource 'plain text content of a specified entry on the PRTS wiki'. It distinguishes from sibling tools which are operator-specific or story-specific.

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 on when to use this tool versus alternatives like search_prts or the operator-specific tools. The description gives no context for appropriate use cases.

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

Deploy Server

Other Tools