Skip to main content
Glama

tracker_search

Read-onlyIdempotent

Search across projects, epics, tasks, and notes by keyword to find relevant information in your project tracker database.

Instructions

Search across ALL entities (projects, epics, tasks, notes) by keyword. Returns categorized results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch keywords
entity_typesNoLimit search to specific entity types (omit for all)
limitNoMax results per entity type

Implementation Reference

  • The handler function 'handleSearch' performs the database queries for the 'tracker_search' tool.
    function handleSearch(args: Record<string, unknown>) {
      const db = getDb();
      const query = args.query as string;
      const entityTypes = (args.entity_types as string[] | undefined) ?? ['project', 'epic', 'task', 'note'];
      const limit = (args.limit as number) ?? 20;
      const pattern = `%${query}%`;
    
      const results: Record<string, unknown[]> = {};
    
      if (entityTypes.includes('project')) {
        results.projects = db
          .prepare('SELECT * FROM projects WHERE name LIKE ? OR description LIKE ? LIMIT ?')
          .all(pattern, pattern, limit);
      }
    
      if (entityTypes.includes('epic')) {
        results.epics = db
          .prepare(
            `SELECT e.*, p.name as project_name
             FROM epics e
             JOIN projects p ON p.id = e.project_id
             WHERE e.name LIKE ? OR e.description LIKE ?
             LIMIT ?`
          )
          .all(pattern, pattern, limit);
      }
    
      if (entityTypes.includes('task')) {
        results.tasks = db
          .prepare(
            `SELECT t.*, e.name as epic_name
             FROM tasks t
             JOIN epics e ON e.id = t.epic_id
             WHERE t.title LIKE ? OR t.description LIKE ?
             LIMIT ?`
          )
          .all(pattern, pattern, limit);
      }
    
      if (entityTypes.includes('note')) {
        results.notes = db
          .prepare('SELECT * FROM notes WHERE title LIKE ? OR content LIKE ? LIMIT ?')
          .all(pattern, pattern, limit);
      }
    
      return results;
    }
  • The definition and input schema for the 'tracker_search' tool.
    {
      name: 'tracker_search',
      description:
        'Search across ALL entities (projects, epics, tasks, notes) by keyword. Returns categorized results.',
      annotations: { title: 'Global Search', readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Search keywords' },
          entity_types: {
            type: 'array',
            items: { type: 'string', enum: ['project', 'epic', 'task', 'note'] },
            description: 'Limit search to specific entity types (omit for all)',
          },
          limit: { type: 'integer', default: 20, description: 'Max results per entity type' },
        },
        required: ['query'],
      },
    },
  • Mapping of the 'tracker_search' tool name to its handler function.
    export const handlers: Record<string, ToolHandler> = {
      tracker_search: handleSearch,
    };
Behavior3/5

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

Annotations already cover key behavioral traits (read-only, non-destructive, idempotent, closed-world). The description adds useful context about the scope ('ALL entities') and return format ('categorized results'), but does not elaborate on pagination, rate limits, or authentication needs beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences that are front-loaded and waste no words. Every sentence directly contributes to understanding the tool's purpose and output, making it highly efficient.

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?

Given the tool's moderate complexity, rich annotations, and full schema coverage, the description is mostly complete. However, the lack of an output schema means the description could better explain the 'categorized results' format, leaving a minor gap in contextual understanding.

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 fully documents all parameters. The description implies keyword-based searching and categorization of results, but does not add significant semantic details beyond what the schema already specifies, such as how 'categorized results' are structured.

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 description clearly states the specific action ('Search across ALL entities') and resources ('projects, epics, tasks, notes'), distinguishing it from sibling tools like note_search or epic_list by emphasizing its global scope across all entity types.

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?

The description provides clear context for when to use this tool ('Search across ALL entities by keyword'), but it does not explicitly mention when not to use it or name specific alternatives among the sibling tools, such as note_search for more targeted searches.

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/spranab/saga-mcp'

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