Skip to main content
Glama
Sign In
indalo-tech

YouGile MCP

by indalo-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Yougile Tasks

yougile_tasks

Manage YouGile tasks: list/search with filters, get by UUID or number, create, update status, deadlines, time tracking, and chat subscribers.

Instructions

YouGile tasks: list/search (filters: columnId, assignedTo, stickerId, title), get by UUID or by number like ID-123, create, update (move via columnId, complete, archive, deadline, timeTracking plan/work hours, checklists, stickers, soft-delete via deleted=true), task chat subscribers. A task's chat id equals the task id (see yougile_chats).

Operations ([access]):

  • list [read]: Получить список задач

  • list_newest [read]: Получить список задач в обратном порядке

  • create [write]: Создать

  • get [read]: Получить по ID

  • update [write]: Изменить

  • get_log [read]: Получить лог задачи

  • get_chat_subscribers [read]: Получить список участников чата задачи

  • set_chat_subscribers [write]: Изменить список участников чата задачи

Call yougile_help('tasks.') for parameters.

Input Schema

NameRequiredDescriptionDefault
paramsNoFlat object with path params, query params and body fields, e.g. {"id": "ID-123", "title": "New title"}. See yougile_help("tool.operation").
confirmNoSet true only after the user explicitly approved a write into a client-facing project (needed only when the tool answered confirmation_required).
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.2
    • changedInput schema / properties / operation / enum
      Previous value: -[
-  "list",
-  "list_newest",
-  "create",
-  "get",
-  "update",
-  "get_chat_subscribers",
-  "set_chat_subscribers"
-]New value: +[
+  "list",
+  "list_newest",
+  "create",
+  "get",
+  "update",
+  "get_log",
+  "get_chat_subscribers",
+  "set_chat_subscribers"
+]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations carry only openWorldHint, so the description must supply behavioral context, and it does: each operation is tagged [read] or [write], it discloses soft-delete semantics (deleted=true), and it notes the confirmation flow via the confirm parameter. It still omits rate limits, permission requirements, and return behavior, keeping it short of a 5.

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?

The overview is front-loaded before the operation list, and each operation is one line. There is some redundancy because every operation name is repeated in English and Russian, but the structure is otherwise clean and scannable.

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 an 8-operation dispatcher with a generic params schema and no output schema, the description covers the operation set, key filters, mutation semantics, and the help-based parameter lookup pattern. It leaves return values, pagination, and the distinction from the single-purpose task siblings unaddressed.

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

Parameters4/5

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

The schema only describes 'params' as a generic flat object, so the description compensates well by enumerating filter keys (columnId, assignedTo, stickerId, title) and update fields (columnId, complete, archive, deadline, timeTracking, checklists, stickers, deleted=true). It defers the full parameter contract to yougile_help, which limits it below a 5.

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?

The description opens with a specific resource ('YouGile tasks') and enumerates the concrete operations (list/search, get, create, update, chat subscribers), so the agent knows exactly what surface this tool exposes. It does not, however, distinguish itself from overlapping siblings such as yougile_create_task, yougile_update_task, yougile_move_task, or yougile_find_tasks.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no routing between this composite tool and the many overlapping task siblings. The only directive is 'Call yougile_help(...) for parameters', which is a parameter-lookup hint, not usage guidance.

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