Skip to main content
Glama
Sign In

InkQuest

by dev.inkquest
OverviewDiscussionsAdmin

Recommend a public story

recommend_story
Read-onlyIdempotent

Recommend up to three public InkQuest stories. Pass hsk_level (1-9 or "HSK 4") to rank Chinese stories by closeness to that band. Optional genre or interests (keywords such as mystery, romance, xianxia, sci-fi) boost matches. Optional target_language is zh or en. Each match includes a short reason and a https://inkquest.dev/stories/{id} link. Only free catalog stories are considered; subscriber-only scenes and user-generated stories are excluded.

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": "recommend_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoGenre or keyword, such as mystery, romance, xianxia, comedy, or science fiction. Case-insensitive.
hsk_levelNoHSK band for Chinese stories. Use an integer 1-9 or a string like "HSK 4". Does not apply to English CEFR stories.
interestsNoFree-text interests, such as "mystery, rainy city" or "sci-fi". Combined with genre.
target_languageNoLearning language: zh for Chinese stories, en for English stories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely new behavioral context: a hard cap of three results, per-match reasons and links, and exclusion of subscriber-only and user-generated content. It stops short of describing behavior when no parameters are supplied.

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?

Four sentences, front-loaded with purpose and scope, then parameter behavior, then output shape, then exclusions. Dense but every sentence carries information; no filler.

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?

No output schema exists, so the description compensates by naming the return shape (short reason plus https://inkquest.dev/stories/{id} link) and the catalog exclusions. It does not state fallback behavior when no optional params are provided, leaving a small gap for a parameterless call.

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?

Schema coverage is 100%, so baseline is 3, but the description adds ranking semantics the schema lacks: hsk_level ranks by 'closeness to that band' rather than exact filtering, and genre/interests 'boost matches' rather than hard-filter. That meaningfully changes how an agent would use these params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource+scope: 'Recommend up to three public InkQuest stories.' It clearly states the catalog constraints and what each result contains, but never names the sibling tools (list_stories, get_story_opening), so the agent must infer the boundary itself.

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?

It explains how to drive the tool (pass hsk_level for band-ranked Chinese stories, genre/interests to boost matches) and marks the other params Optional, but gives no explicit when-to-use / when-not-to-use guidance versus list_stories or get_story_opening.

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

All InkQuest toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources