Skip to main content
Glama

find_task

Retrieve a task's ID and outline ID by searching its title, eliminating the need to list all tasks.

Instructions

Look up tasks by title, returning lightweight identifiers.

Removes the "list everything → grep → use ID" pattern when an agent knows the title but not the uniqueID.

Args: name: Title to match. Case-insensitive substring match by default. exact: When True, only return tasks whose title equals name exactly (case-sensitive). When False, returns every descendant whose title contains name (case-insensitive).

Returns: JSON array of {"id", "title", "outline_id"}. Empty array if nothing matches. Order matches outline traversal (depth-first, children in document order).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
exactNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it is a read operation, returns lightweight identifiers, default case-insensitive substring matching, exact option, empty array on no match, and depth-first order. This covers all essential behavioral aspects.

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 well-structured with a clear one-sentence purpose, a context paragraph, and formatted Args/Returns sections. Every sentence adds value with no redundancy.

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?

Given the tool's low complexity (2 parameters, no annotations, an output schema mentioned), the description provides complete information: what it does, when to use, parameter semantics, return format, and ordering. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does so effectively by explaining that 'name' is matched case-insensitively by default, and 'exact' changes to exact case-sensitive match. It also describes the return format, adding meaning beyond the schema.

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 verb 'look up' and the resource 'tasks by title', with a specific goal: returning lightweight identifiers. It explicitly contrasts with the 'list everything → grep → use ID' pattern, distinguishing it from more extensive listing tools like query_tasks.

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 explicitly tells when to use this tool: 'when an agent knows the title but not the uniqueID.' It also explains the two matching modes (default case-insensitive substring, exact case-sensitive). However, it does not explicitly mention alternatives like get_task for when the ID is known, leaving a minor gap.

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/johntrandall/omniplan-mcp'

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