Skip to main content
Glama
Sign In
YouGile MCP

YouGile MCP

by indalo-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Yougile Find Tasks

yougile_find_tasks
Read-only

Find tasks by project, board, column, assignee, title words, or task number; filter by open/completed status and completion dates to locate overdue or archived work.

Instructions

Find tasks by project/board/column names, assignee and title words. Without a place, searches the workspace's default project if one is set, else the whole company. Completed tasks show completed_at; tasks in a column that counts as done but not marked completed show done_by_column: true. completed_since/completed_until select tasks completed in a period, newest first — those unmarked cards included, dated by the task's history (date_from_history: true; history_unchecked when some logs were not read). Open tasks past their deadline show overdue: true.

Input Schema

NameRequiredDescriptionDefault
textNoWords from the title, or a task number
boardNoBoard name or "Project / Board"
limitNo
columnNoColumn name (needs a board or default)
statusNoDefault "open", or "any" when a column is given
projectNoProject name
assigneeNoName, email or "me"
completed_sinceNoOnly tasks completed on or after this date (implies completed)
completed_untilNoOnly tasks completed on or before this date (implies completed)
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / completed_since
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only tasks completed on or after this date (implies completed)"
+}
    • addedInput schema / properties / completed_until
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only tasks completed on or before this date (implies completed)"
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

With only readOnlyHint=true provided and no output schema, the description carries the disclosure burden and does so unusually well: it explains result fields (completed_at, done_by_column, overdue, date_from_history), the newest-first ordering of date-range results, and a genuine edge case (history_unchecked when logs weren't fully read). This is far beyond what the annotations cover.

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?

Purpose is front-loaded in the first clause, and the subsequent sentences each convey a distinct behavioral fact (scope default, done-by-column, date-range ordering, overdue). The parenthetical nesting around date_from_history/history_unchecked is dense but each clause still earns its place.

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?

For a 10-parameter search with no output schema, it covers scope defaults and return-value semantics thoroughly. Gaps remain minor: limit (50/200) and include_archived are never mentioned, and there is no pagination guidance, but neither undermines 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?

Schema coverage is 80%, so the schema already documents text, board, column, status, project, assignee, and the completion-date params. The description restates the same facets and adds only the 'implies completed' nuance, which the schema also carries, so it adds marginal value over the structured fields. Baseline 3 is appropriate.

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 (Find) and resource (tasks) plus the searchable facets (project/board/column names, assignee, title words), so the agent knows exactly what retrieval this performs. It does not, however, differentiate itself from sibling yougile_tasks or yougile_task, leaving the boundary between the find/list/get tools 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?

It documents default resolution behavior ('without a place, searches the workspace's default project if one is set, else the whole company') and that completed_since/until imply completed, which is useful context. But it never states when to prefer this tool over yougile_tasks/yougile_task or any exclusion.

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

Deploy Server

Other Tools