Skip to main content
Glama

novel_semantic_search

Find relevant passages in a book by natural-language query with local semantic search, returning matching paragraphs offline at zero token cost.

Instructions

本地语义检索(0 token):自然语言搜相关段落。

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": {
      "book": "<book>",
      "query": "<query>"
    },
    "name": "novel_semantic_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo条数(默认5,上限10)
bookYes书名
rootNo书库根
queryYes语义描述

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv8.0.0
    • changedInput schema / properties / book / description
      Previous value: -"书名。"New value: +"书名"
    • changedInput schema / properties / query / description
      Previous value: -"要检索的语义描述,如「与血统秘密相关的段落」「女主压抑克制的时刻」。自然语言越具体越好。"New value: +"语义描述"
    • changedInput schema / properties / root / description
      Previous value: -"章节库根目录(含 novels 子目录)。"New value: +"书库根"
    • changedInput schema / properties / top / description
      Previous value: -"返回条数(默认 5,最大 10)。"New value: +"条数(默认5,上限10)"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose two genuinely useful behavioral traits: the search runs locally and consumes no tokens. However, it says nothing about how results are returned or ranked, whether an index must already exist, or whether results are truncated by the default top=5.

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?

A single compact sentence with the two key facts (local, zero token) front-loaded and no filler. It is arguably too terse, but every word earns its place.

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?

For a four-parameter tool with full schema coverage and no output schema, the description covers the core purpose but omits result shape, ranking, and prerequisites such as index availability. Adequate to invoke the tool, incomplete about what to expect.

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?

Schema description coverage is 100%, so parameters (book, query, top, root) are already documented in the schema. The description adds no additional meaning about query phrasing, scoping to one book, or how root interacts with book, so the baseline 3 applies.

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?

Description contains a clear verb plus resource ("语义检索"/semantic search on "段落"/passages) and adds the distinguishing property "本地...0 token". An agent can immediately tell this is a local, cost-free semantic lookup rather than a file-read or keyword tool, though no sibling is named explicitly.

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 "0 token" qualifier implicitly signals when this tool is preferable to other lookups, but there is no explicit when-to-use or when-not-to-use guidance and no sibling is referenced (e.g. vs novel_read or novel_keywords). Usage must be inferred from the cost hint.

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