Skip to main content
Glama

ugreen_search_results

Read-onlyIdempotent

Continue reading paginated NAS search results using a task_id from a prior search, with offset/limit controls and name/asc order preserved.

Instructions

继续读取搜索结果。task_id 必须来自搜索返回值,排序保持 name/asc。

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": {
      "task_id": "<task_id>"
    },
    "name": "ugreen_search_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and idempotency are covered. The description adds two useful facts beyond them: that ordering is fixed at name/asc, and that task_id must originate from a search response. It does not say what happens when offset exceeds the result count or how the caller learns that paging is exhausted.

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?

Two short clauses with no filler, and the continuation purpose is front-loaded ahead of the task_id constraint. It is efficient, though the extreme terseness leaves real gaps that a slightly longer text could have closed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pagination tool with a 0%-described schema and no output schema, the definition should explain how limit and offset interact and when paging is complete. Neither is addressed, so an agent must infer the paging protocol from the raw schema numbers, and there is no output schema to compensate.

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 schema has 0% description coverage and three parameters, so the description must supply meaning. It does explain the provenance constraint on task_id, the single required parameter, which is valuable, but it says nothing about limit and offset even though those control the paging this tool exists for.

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 Chinese description identifies a specific action (继续读取 = continue reading) on a specific resource (搜索结果 = search results), and the word 继续 implicitly distinguishes this tool from the initial ugreen_search call. It never names ugreen_search explicitly, so a small amount of the sibling differentiation is left implicit.

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?

It gives a concrete prerequisite: task_id 必须来自搜索返回值 (task_id must come from the search return value), which effectively tells the agent that this tool is a follow-up to a prior search and cannot be called standalone. It does not explicitly state when to stop paging or name the alternative tool, but the continuation condition is clear.

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