Skip to main content
Glama
Sign In
prts-mcp

prts-mcp

by 3aKHP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

read_story

Retrieve the full script of a single story chapter. Provide the story key to get dialogue, with option to include or exclude narration.

Instructions

读取单章剧情的完整台词。

Args:
    story_key: 章节 key，如 "activities/act31side/level_act31side_01_beg"（可从 list_stories 获取）。
    include_narration: 是否包含旁白和场景描述，默认 True。

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": {
      "story_key": "<story_key>"
    },
    "name": "read_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
story_keyYes
include_narrationNo

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

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the operation is a read and describes parameters, but does not disclose error handling, required permissions, or behavior for invalid input. Adequate but minimal.

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?

Extremely concise: two sentences plus bullet-like argument descriptions. Every sentence is necessary and front-loaded with the core purpose. No redundancy or fluff.

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?

The tool is simple with two parameters and an output schema exists. The description adequately covers what the tool does, the required and optional parameters, and hints at integration with list_stories. No additional context needed for the given complexity.

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?

With 0% schema description coverage, the description fully compensates by explaining the purpose of include_narration (whether to include narration/scene descriptions) and provides an example and source for story_key. Adds significant value beyond the schema's type info.

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?

Description clearly states verb ('读取' meaning read) and resource ('单章剧情的完整台词' meaning complete dialogue of a single story chapter). It distinguishes from siblings like list_stories (listing) and read_activity (reading activity data) by focusing specifically on dialogue content.

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 provides a concrete example for story_key and notes it can be obtained from list_stories, but does not explicitly state when to use vs alternatives or when not to use. Usage is implied rather than explicitly guided.

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