Skip to main content
Glama

search

Find todos, projects, and tasks in your Things 3 app by entering search queries to locate specific items quickly.

Instructions

搜索Things中的待办事项、项目等。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo搜索查询文本

Implementation Reference

  • The handler function that implements the 'search' tool logic by building and opening a Things URL scheme for searching.
    async handleSearch(args) {
      const url = buildThingsUrl('search', args);
      await this.openThingsUrl(url);
    
      return {
        content: [
          {
            type: 'text',
            text: `🔍 搜索命令已发送${args.query ? `: ${args.query}` : ''}`,
          },
        ],
      };
    }
  • Input schema for the 'search' tool, defining the required 'query' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: '搜索查询文本',
        },
      },
    },
  • src/index.js:339-351 (registration)
    Tool registration in the ListTools response, providing name, description, and schema.
    {
      name: 'search',
      description: '搜索Things中的待办事项、项目等。',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: '搜索查询文本',
          },
        },
      },
    },
  • src/index.js:441-442 (registration)
    Dispatch registration in the CallToolRequestSchema handler switch statement.
    case 'search':
      return await this.handleSearch(args);
  • Helper utility function called by the search handler to construct the search URL: buildThingsUrl('search', args).
    export function buildThingsUrl(command, params = {}) {
      const baseUrl = `things:///${command}`;
      const queryString = buildQueryString(params);
    
      if (!queryString) {
        return baseUrl;
      }
    
      return `${baseUrl}?${queryString}`;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool performs a search but doesn't describe how results are returned (e.g., format, pagination), what happens on no matches, or any constraints (e.g., search scope, performance limits). For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 description is a single, efficient sentence in Chinese that directly states the tool's function. It's front-loaded with the core action ('搜索' - search) and target ('Things'), with no unnecessary words. However, it could be slightly more structured by explicitly listing searchable item types instead of using '等' (etc.).

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?

Given the complexity of a search operation, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the search returns (e.g., list of items, details), how results are formatted, or any behavioral aspects like error handling. For a tool that likely returns varied data, more context is needed to guide effective use.

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 input schema has 100% description coverage, with the 'query' parameter documented as '搜索查询文本' (search query text). The description doesn't add any meaning beyond this, such as query syntax examples or supported search operators. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter documentation.

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

Purpose3/5

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

The description states the tool searches for '待办事项、项目等' (todos, projects, etc.) in Things, which provides a general purpose. However, it's vague about the exact scope ('等' means 'etc.') and doesn't clearly distinguish from sibling tools like 'show' or differentiate between searching todos vs. projects. It specifies the verb '搜索' (search) and target 'Things', but lacks precision.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention when to prefer 'search' over sibling tools like 'show' (which might display items) or how it complements other tools (e.g., 'add_todo', 'update_project'). The description implies a general search function but offers no context for selection among similar operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mieluoxxx/things_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server