Skip to main content
Glama

标题搜索

gwl_search
Read-onlyIdempotent

Search document, organization, group, and discover titles, then return permission-filtered paginated results with type and tag filters.

Instructions

按标题跨对象搜索(文档 / 组织 / 组 / 发现条目),逐条判权后分页返回。 data 里除分页包络外还有 q、types[]、counts{document,organization,group,discover},items 每项含 type、id、title、summary、icon、url、matched 与范围字段。 types 可多值;传 discover_item 会被映射成上游的 discover。 q 必填且不超过 64 个字符,否则 400。命中量超过扫描上限时返回 scan_truncated=true。

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": {
      "q": "<q>"
    },
    "name": "gwl_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes标题关键词(1~64 个字符)。
pageNo页码,从 1 开始。非法值由上游回落到 1,不报错。
sizeNo每页条数,1~100;超过 100 上游按 100 处理。
tagsNo标签过滤(最多 8 个)。
scopeNo文档范围过滤(仅对文档类结果生效)。
typesNo限定搜索对象类型;省略=全部。discover_item 会自动映射为上游的 discover。
tag_modeNo标签命中方式:all=同时具备,any=任一具备。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the supplied annotations (readOnlyHint/openWorldHint/idempotentHint/destructiveHint=false), the description adds real behavioral context: per-item permission judgement (逐条判权) before results are returned, a 400 error when q is missing or over 64 characters, and scan_truncated=true when hits exceed the scan cap. It does not cover rate limits or ordering, so it does not reach 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?

The purpose is front-loaded in the first sentence, followed by return shape, type mapping, and hard constraints in descending order of importance. Every line carries information, though the return-value enumeration overlaps with the output schema and trims a bit of efficiency.

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 7-parameter search tool with an existing output schema, the description covers what matters: cross-object scope, per-item permission filtering, pagination, and truncation signaling. It is slightly redundant in re-describing return fields that the output schema already defines, but nothing an agent needs in order to call it correctly is missing.

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 the schema already documents q's 1–64 length, page/size fallbacks, tags limits, scope, and tag_mode. The description only repeats the q constraint and the discover_item→discover mapping that is already present in the schema, adding no new parameter meaning, so the baseline of 3 applies.

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 first sentence gives a specific verb (搜索) + resource (标题) + scope (跨对象:文档 / 组织 / 组 / 发现条目) and adds that results are permission-filtered and paginated. That is enough for an agent to distinguish it from siblings such as gwl_list_documents or gwl_get_document without opening the schema.

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 implied by the semantics of title search and by the note that types may be multi-valued and that omitting types means all types. However, the description never states when to prefer this tool over gwl_list_documents, gwl_list_my_documents, or gwl_get_tag_facets, nor does it set exclusions or prerequisites, so the agent is left to infer routing.

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