Skip to main content
Glama

query_method

Retrieves the most relevant passages from methodology documents 00-10 by keyword, supporting multiple space-separated terms to look up concepts such as volume clustering, negation patterns, golden three chapters, or hook density.

Instructions

检索方法论文档(00-10 号 11 篇):按关键词返回最相关片段。例如查"卷群"、"否定式"、"黄金三章"、"爽点密度"、"听书"。

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

Input Schema

NameRequiredDescriptionDefault
queryYes关键词,支持多个(空格分隔)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal two useful traits beyond the schema: the corpus is a fixed set of eleven methodology documents, and the result is ranked relevant fragments rather than whole documents. It omits how many fragments come back, whether ranking is by relevance or recency, and whether an empty result is possible.

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?

A single tight sentence front-loads the resource and scope, then states the return behavior, with the example keywords earning their place by demonstrating the vocabulary expected. Nothing is redundant.

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?

For a one-parameter read-only lookup with no output schema, the definition covers corpus, input style, and return type adequately. The only real gap is a brief note on result volume or how to interpret returned fragments, which is minor at this complexity.

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?

With a single parameter at 100% schema description coverage, the baseline of 3 applies. The description does add concrete keyword examples that illustrate the granularity expected, and repeats that multiple space-separated keywords are supported, but adds no syntax or matching-behavior detail (e.g. AND vs OR across multiple terms) beyond the schema.

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 states a specific verb and resource ('检索方法论文档') and pins the corpus scope to eleven documents numbered 00-10, so the agent knows exactly what knowledge base is being searched. It also clarifies the return shape ('按关键词返回最相关片段'), which separates it from the sibling checkers and planners, though it never names an alternative tool 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?

Usage is only implied: the example keywords ('卷群', '否定式', '黄金三章', '爽点密度', '听书') show the kind of concept this tool answers questions about. There is no statement of when to prefer this over siblings like check_pacing or next_chapter_brief, and no when-not-to-use guidance or prerequisites.

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