Skip to main content
Glama
Sign In

Zentrik

by ai.zentrik
OverviewDiscussionsAdmin

tasks_get

Read-onlyIdempotent

Get task instructions, identifier (LOY-142), workflow state, labels, parent, dependencies, owner, sprint and sourceIdeaId/sourceEvidenceId. id accepts the task id or its identifier. availableStates lists the team workflow states tasks.update accepts as workflowStateId. Follow the idea with ideas.get and ideas.get_evidence; fetch direct evidence with signal_evidence.get. Read PR attachments with tasks.list_pull_requests.

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": {
      "teamId": "<teamId>",
      "id": "<id>"
    },
    "name": "tasks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id, or its identifier such as LOY-142.
teamIdYes

Output Schema

NameRequiredDescriptionDefault
itemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Task id, or its identifier such as LOY-142."
    • removedInput schema / properties / id / format
      Removed value: -"uuid"
    • addedInput schema / properties / id / maxLength
      Added value: +64
    • addedInput schema / properties / id / minLength
      Added value: +1
    • removedInput schema / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed4 schema fields changed
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / teamId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / item / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "teamId",
-  "id",
-  "llm_model"
-]New value: +[
+  "teamId",
+  "id"
+]
  4. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "teamId",
-  "id"
-]New value: +[
+  "teamId",
+  "id",
+  "llm_model"
+]
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: id accepts either a raw id or a human identifier like LOY-142, and availableStates surfaces the valid workflowStateId values that tasks.update will accept. It does not cover failure modes (unknown id, cross-team access), which keeps 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?

Four tight sentences with the returned fields front-loaded, followed by parameter nuance and then cross-tool routing. The compressed list style is dense but every clause carries information; nothing is filler.

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?

An output schema exists, so return values need not be spelled out, yet the description still tells the agent what the payload covers and how to follow references to sibling tools. The main remaining gap is teamId, which is required but unexplained anywhere in the description.

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 50%: id is documented in the schema, teamId is not. The description restates the id-as-identifier behavior already present in the schema and never explains teamId's role (scoping the lookup to a team), so it only partially compensates for the coverage gap. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Get task") and enumerates exactly what comes back: instructions, identifier, workflow state, labels, parent, dependencies, owner, sprint, and source linkage fields. An agent can distinguish this from tasks_list or tasks_update without inspecting any schema.

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 single-task lookup use case is implicit in the field enumeration, and the description explicitly routes follow-ups: ideas.get / ideas.get_evidence for the originating idea, signal_evidence.get for direct evidence, tasks.list_pull_requests for PR attachments. It does not contrast with tasks_list, but the guidance it does give is concrete.

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

All Zentrik toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources