Skip to main content
Glama

Coline

Find a task

find_task
Read-onlyIdempotent

Finds a task by its key (like ENG-42) or by words in its title, on boards the person can open.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "reference": "<reference>"
    },
    "name": "find_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
referenceYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful scope ('on boards the person can open'), meaning results are permission-filtered. It omits, however, what happens with multiple title matches and that results are capped (limit defaults to 5, max 10).

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?

A single sentence that front-loads the verb and both accepted input forms, with the permission scope appended. No filler, nothing redundant.

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

Completeness3/5

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

An output schema exists, so return value description is not needed, and the permission constraint is stated. What is missing for a three-parameter search tool is ambiguity behavior — multiple matches, the result cap, and how to choose between a key lookup and a title search.

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 coverage is 33%, so the description carries real weight for the 'reference' parameter and does so well by giving a concrete key format example (ENG-42) and the title-word alternative. The 'limit' parameter is entirely undiscussed in both schema and description, leaving the agent unaware that matches are truncated and ambiguous title searches return only a handful of results.

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?

States a specific verb (finds) and resource (a task) plus the two lookup modes — key like ENG-42 or title words — so the agent knows exactly what input shapes work. It does not distinguish itself from the sibling get_task, which likely handles single-record retrieval, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by naming the two search modes (key vs. title words), which tells an agent when this tool is applicable. There is no explicit guidance on when NOT to use it, nor a pointer to get_task or other task-lookup tools, so the agent must guess at alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources