Skip to main content
Glama

show

Navigate to and display areas, projects, tags, todos, or built-in lists like inbox or today in Things 3 task management.

Instructions

导航到并显示区域、项目、标签、待办事项或内置列表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID或内置列表名(inbox, today, anytime, upcoming, someday, logbook等)
queryNo查询名称(如果未提供id)
filterNo按标签筛选,逗号分隔

Implementation Reference

  • The handler function for the 'show' tool. It constructs a Things URL using buildThingsUrl('show', args) and opens it via openThingsUrl to navigate and display the specified item or list in Things.
    async handleShow(args) {
      const url = buildThingsUrl('show', args);
      await this.openThingsUrl(url);
    
      return {
        content: [
          {
            type: 'text',
            text: `✅ 导航命令已发送${args.id ? ` (${args.id})` : args.query ? ` (${args.query})` : ''}`,
          },
        ],
      };
    }
  • src/index.js:318-338 (registration)
    Registration of the 'show' tool in the MCP server's tool list, including name, description, and input schema definition.
    {
      name: 'show',
      description: '导航到并显示区域、项目、标签、待办事项或内置列表。',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'ID或内置列表名(inbox, today, anytime, upcoming, someday, logbook等)',
          },
          query: {
            type: 'string',
            description: '查询名称(如果未提供id)',
          },
          filter: {
            type: 'string',
            description: '按标签筛选,逗号分隔',
          },
        },
      },
    },
  • Helper function used by the 'show' handler to construct the Things URL scheme for the 'show' command.
    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. It states the tool '显示' (displays) items, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, how it handles errors, if it's idempotent, or what the output format is. For a tool with no annotations, 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, concise sentence that efficiently states the tool's purpose. It's front-loaded with the core action and resources, with no unnecessary words. However, it could be slightly more structured by explicitly mentioning the parameters or usage context.

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 (3 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain how the tool behaves, what it returns, or how to use it effectively with siblings like 'search'. For a navigation/display tool with multiple parameters, more context is needed to ensure proper usage.

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 description doesn't add any parameter-specific information beyond what's in the input schema, which has 100% description coverage. It mentions the types of items (areas, projects, tags, todos, built-in lists) that can be shown, but this doesn't clarify the semantics of the three parameters (id, query, filter). With high schema coverage, the baseline is 3, and the description doesn't compensate with additional insights.

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 clearly states the tool's purpose: '导航到并显示区域、项目、标签、待办事项或内置列表' (Navigate to and display areas, projects, tags, todos, or built-in lists). It specifies the verb '显示' (display) and lists the resources it can show. However, it doesn't explicitly differentiate from sibling tools like 'search', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use 'show' versus 'search' (a sibling tool) or other tools like 'add_todo'. There's no context about prerequisites, exclusions, or typical use cases.

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