Skip to main content
Glama

things_show

Navigate to specific to-dos, projects, or lists in Things 3 using IDs or queries to access inbox, today, upcoming, and other views with optional tag filtering.

Instructions

Navigate to a specific item or list in Things

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of a specific to-do, project, or area
queryNoNavigate to a list: inbox, today, anytime, upcoming, someday, logbook, trash
filterNoFilter by tags when showing a list

Implementation Reference

  • The execute method for the things_show tool, which handles the tool invocation and calls executeThingsURL.
    async execute(toolName: string, params: ShowParams): Promise<string> {
      if (toolName !== 'things_show') {
        throw new Error(`Unknown tool: ${toolName}`);
      }
      
      await executeThingsURL('show', params);
      
      return params.id 
        ? '🔍 Navigated to item in Things'
        : `🔍 Navigated to: ${params.query}`;
    }
  • src/tools/show.ts:9-15 (registration)
    Registration of the things_show tool definition, including its name, description, and schema.
    protected definitions: ToolDefinition<ShowParams>[] = [
      {
        name: 'things_show',
        description: 'Navigate to a specific item or list in Things',
        schema: ShowSchema
      }
    ];
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 disclosure burden. While 'Navigate' implies a read-only UI operation, the description does not confirm side effects, error handling when IDs are invalid, or whether this opens the Things application externally.

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 single-sentence description is appropriately front-loaded with no wasted words. However, given the complexity of the Things tool ecosystem (20+ siblings), it is slightly too terse to provide sufficient context for correct tool selection.

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?

Lacks guidance on distinguishing this from things_get_list and other list retrieval tools. Without an output schema or annotations, and with all parameters being optional, the description should explain the navigation behavior and expected outcomes to ensure correct invocation.

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 100% schema description coverage, the schema adequately documents all three parameters (id, query, filter). The description aligns with the schema by mentioning 'item or list' but adds no additional syntax details, format constraints, or usage examples beyond what the schema provides.

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 uses a specific verb ('Navigate') and resource ('item or list in Things'), clearly indicating a UI-focused operation. However, it does not explicitly distinguish from the numerous 'things_get_*' siblings which likely retrieve data without navigating the UI, potentially causing selection confusion.

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 explicit when-to-use or when-not-to-use guidance is provided. Given the many sibling tools for retrieving lists (things_get_inbox, things_get_today, things_get_list), the description fails to clarify whether to use this for UI navigation versus data retrieval.

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/hildersantos/things-mcp'

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