Skip to main content
Glama
Sign In
prts-mcp

prts-mcp

by 3aKHP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

list_stories

Retrieve story chapters for a specified event ID, ordered officially. Input the event ID to get the complete list.

Instructions

列出指定活动的所有剧情章节（按官方顺序排列）。

Args:
    event_id: 活动 ID，如 "act31side"（可从 list_story_events 获取）。

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": {
      "event_id": "<event_id>"
    },
    "name": "list_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes

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/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. It discloses that output is ordered, but omits details about error handling, permissions, or side effects. This is insufficient for a tool with no safety annotations.

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, with the purpose stated in a single sentence plus an args section. Every piece of text adds value.

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?

Given the simple tool (one required string param, no enums, output schema exists), the description covers the core functionality adequately. It lacks guidance on invalid inputs or empty results, but the presence of an output schema mitigates the need for return value details.

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 schema has 0% description coverage, but the description adds meaningful context: event_id is an activity ID (e.g., 'act31side') retrievable from list_story_events. This clarifies the parameter beyond the bare schema.

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 ('列出所有剧情章节') and the resource ('指定活动'), with explicit mention of ordering ('按官方顺序排列'). It distinguishes from siblings like list_story_events and read_story.

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 explains that event_id can be obtained from list_story_events, providing a direct link for when to use this tool. However, it does not explicitly state when not to use it or mention alternative tools.

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