Glasscubes MCP server

Get task

get_task

Read-only

Retrieve detailed information for a specific task using its ID, including state, dates, assignees, labels, and attachments. Optionally include contact details.

Instructions

One task with its state (NEW, STARTED, COMPLETED), dates, assignees, labels, attachment titles and form submissions.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task ID
`include_contact_details`	No	Include email addresses, event locations and the links into a client's view of a request, and stop redacting emails, phone numbers, postcodes and NI numbers from names, labels and other free text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating the returned payload, but it never discloses that fields are redacted by default or that include_contact_details unlocks PII — a meaningful behavioral trait left entirely to the schema.

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?

A single tight sentence with no wasted words, front-loading the resource and the returned fields. It is a noun fragment with no verb, which slightly weakens the opening but keeps it efficient.

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?

With no output schema, the description does useful work by enumerating the returned data categories. Combined with full schema coverage and read-only annotations, an agent has enough to call it correctly; only error/permission behavior and default-redaction implications are unstated.

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 description coverage is 100%, so both parameters (including the redaction semantics of include_contact_details) are already fully documented in the schema. The description adds no syntax, format, or constraint detail beyond what the schema provides, making the baseline of 3 correct.

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 states a specific resource and enumerates exactly what is returned ('One task with its state (NEW, STARTED, COMPLETED), dates, assignees, labels, attachment titles and form submissions'). The singular 'One task' implicitly distinguishes it from the sibling list_tasks, though no sibling is named explicitly.

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 when-to-use guidance, no statement that a task_id is required to invoke it, and no routing to alternatives such as list_tasks for multiple records. Usage must be inferred purely from the name and the singular noun phrase.

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

Deploy Server