Skip to main content
Glama

Find similar tasks

find_similar_tasks
Read-only

Find existing OmniFocus tasks with similar names before creating a new one. Returns ranked matches with similarity scores to reuse an existing task and avoid duplicates.

Instructions

Find existing OmniFocus tasks whose names are similar to a proposed new task name. Run this BEFORE creating a task that might already exist — it returns ranked matches with similarity scores and task IDs so you can reuse an existing task instead of creating a duplicate. Tolerant of typos, word reordering, and partial names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe task name you are about to create. Existing tasks are ranked by how closely their names match this.
freshNoBypass the process-local cache. Other clients and GUI changes may otherwise remain cached for the advertised TTL.
limitNoMaximum number of matches to return (1-20). Default 5.
minScoreNoMinimum similarity score (0-1) a task must reach to be listed. Default 0.35. Raise it (e.g. 0.6) for near-exact matches only; lower it to cast a wider net.
includeCompletedNoAlso search completed and dropped tasks. Default false — a finished task is rarely the one you want to reuse, but this is useful for checking whether something was already done.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
toolYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already signals a safe read operation. The description adds valuable behavioral context beyond that: it returns 'ranked matches with similarity scores and task IDs' and is 'tolerant of typos, word reordering, and partial names.' This explains matching semantics without contradicting the annotation.

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?

Three sentences, each earning its place: purpose, usage timing, and matching tolerance. Information is front-loaded and there is no filler, repetition, or vague language. It is both concise and information-dense.

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

Completeness5/5

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

The description covers the core workflow, result type, and matching behavior. With a fully self-documenting schema, readOnlyHint annotation, and an output schema present, nothing essential is missing for an agent to select and invoke the tool correctly.

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%, and each parameter already has a detailed description (e.g., minScore explains raising/lowering thresholds). The tool description adds marginal value by framing the name parameter as 'the task name you are about to create' and mentioning tolerance behaviors, but it does not need to restate schema information.

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 opens with a specific verb and resource: 'Find existing OmniFocus tasks whose names are similar to a proposed new task name.' It clearly identifies the tool's purpose and distinguishes it from general search or filter tools by focusing on similarity matching and duplicate prevention. The workflow context ('Run this BEFORE creating a task...') further differentiates it from creation and editing siblings.

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 gives explicit when-to-use guidance: 'Run this BEFORE creating a task that might already exist' and explains the goal of reusing an existing task to avoid duplicates. It does not name specific alternative tools or give exclusions, but the context is clear enough for an agent to route to this tool during task creation.

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