Skip to main content
Glama
YOLKINS
by YOLKINS

Get one Weeek task

weeek_get_task
Read-onlyIdempotent

Fetch a single Weeek task by ID, returning its full description along with title, priority, and project info. Use when you need complete task details from a known task ID.

Instructions

PRIMARY tool for fetching a single Weeek task by task_id ({id, title, description, completed, projectId, priority, type}). DISTINCT from weeek_list_tasks — this is the only tool that returns the full description field. Use when an agent already has a specific id and needs full details; unknown ids surface as weeek_get_task failed (weeek_not_found): ….

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesWeeek task identifier (from weeek_list_tasks or the Weeek UI)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStable Weeek task identifier
typeYesTask type (action | meet | call)
titleYesTask title
userIdYesUUID of the primary assignee (Weeek member id, matches weeek_list_members.id). Null if the task is unassigned.
priorityYesPriority code (commonly 0=Low, 1=Medium, 2=High, 3=Hold), or null when no priority is set. The range is not guaranteed by the API.
assigneesYesUUIDs of every assignee on the task (matches weeek_list_members.id). Empty if the task is unassigned; includes userId on assigned tasks.
completedYesWhether the task is completed
projectIdYesOwning project id
truncatedYesTrue if the response was clipped by the server's MAX_RESPONSE_CHARS gate. Only `description` is clipped (other fields are fixed-shape); the agent can re-issue with raised MAX_RESPONSE_CHARS in the server env to see the full text.
descriptionYesTask description (nullable). May end with the marker '…[truncated]' if the response hit MAX_RESPONSE_CHARS — see the truncated field.
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it specifies that this is the only tool returning the full description field, and describes the error format for unknown ids (weeek_not_found). This enriches the agent's understanding of the tool's behavior.

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 concise and well-structured: it opens with the primary purpose, followed by a distinct sibling differentiation, usage guidance, and error behavior. No word is wasted, and all key information is front-loaded.

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 (one parameter), rich annotations, and presence of an output schema, the description is complete. It covers purpose, usage, sibling distinction, return fields, and error behavior—enough for an agent to select and invoke the tool correctly without additional documentation.

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?

The input schema provides 100% coverage for the single parameter task_id, with a clear description of where to obtain it (from weeek_list_tasks or the Weeek UI) and a minimum constraint. The tool description itself does not add additional parameter-level semantics, so the baseline of 3 applies.

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 tool fetches a single Weeek task by task_id, lists the returned fields, and explicitly distinguishes itself from weeek_list_tasks by being the only tool that returns the full description field. This makes the purpose unambiguous and differentiated.

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

Usage Guidelines5/5

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

It provides explicit when-to-use guidance: 'Use when an agent already has a specific id and needs full details.' It also names the alternative (weeek_list_tasks) and explains the error behavior for unknown ids, giving clear decision-making context.

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/YOLKINS/weeek-mcp'

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