Skip to main content
Glama

Warm Night Fishing (暖夜垂钓)

by cloud.aevia

fishing_share_card

生成可分享的图鉴 / 稀有时刻分享卡(kind: encyclopedia | moment);也可填 fish:<中文鱼名> 给某条已钓到、收录进图鉴的鱼单独出一张卡。 / Generate a shareable card (encyclopedia | moment); optionally name a caught fish to card it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fishNo可选:给某条你已经钓到、收录进图鉴的鱼单独出一张卡,填它的中文名(如 鲫鱼);没钓到过或名字对不上就不出卡。 / Optional: name a fish you've already caught (Chinese name, e.g. 鲫鱼) to card that one fish; no card if it's uncaught or the name doesn't match.
kindYes卡片类型:encyclopedia(图鉴进度)或 moment(近期稀有时刻)。 / Card kind: 'encyclopedia' (dex progress) or 'moment' (recent rare moment).
player_codeNo你的存档码(形如 WNF-XXXX-XXXX-XXXX),用来给这个存档出分享卡。不填就先 fishing_play 玩一竿拿到码,再来出卡。 / Your save code (e.g. WNF-XXXX-XXXX-XXXX) to card this save; play once first if you don't have one.

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden of disclosure. It reveals a key behavioral rule: if the fish is uncaught or the name doesn't match, no card is generated. However, it does not mention side effects, authentication needs, or rate limits, leaving some gaps.

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 two concise bilingual lines, front-loaded with the action and resource, and every sentence serves a purpose. No wasted words.

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?

The description explains the core purpose and a critical conditional behavior, and the schema fully documents parameters. For a card-generation tool, this is complete enough, even without an output schema.

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

Parameters3/5

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

The input schema descriptions are 100% comprehensive, documenting all three parameters with bilingual explanations. The tool description adds little beyond what the schema already states, so the baseline of 3 is appropriate.

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 'Generate a shareable card (encyclopedia | moment)' with an optional fish name, providing a specific verb and resource. This distinguishes it from sibling tools like fishing_play or fishing_save_info.

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 implies usage for generating cards and explains the optional fish parameter, giving clear context for when to use it. It does not explicitly exclude alternatives, but the sibling tools are clearly different actions, so no confusion arises.

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

All Warm Night Fishing (暖夜垂钓) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct aspect: manual, new game, gameplay actions, save metadata, and card generation. There is no overlap; even the broad 'play' tool is clearly the single channel for game commands, distinct from the others.

Naming Consistency4/5

All tools share the 'fishing_' prefix, which creates a strong pattern. However, the suffixes mix conventions: 'play', 'save_info', and 'share_card' are verb_noun, while 'manual' is a noun and 'new_game' is adjective_noun, a minor deviation from a fully consistent verb_noun style.

Tool Count5/5

With 5 tools, the server is well-scoped for a fishing game. It covers instructions, gameplay, lifecycle, metadata, and social features without unnecessary bloat, making the count ideal for the purpose.

Completeness5/5

The tool set provides complete coverage of the game's core loop: learn via manual, restart with new_game, all actions through play, save metadata via save_info, and sharing through share_card. No obvious gaps exist; the single gameplay channel handles all in-game operations.

Resources