Skip to main content
Glama

get_task_file

Read-only

Retrieve a Kanboard task attachment by file_id and return images as images or text files as text for direct viewing in MCP clients.

Instructions

Read a task attachment: images are returned as images, text files as text.

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": {
      "file_id": "<file_id>"
    },
    "name": "get_task_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesAttachment file_id from get_task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, open-world operation, so the safety profile is covered. The description does add genuinely new information beyond annotations — that return form depends on content type (images as images, text as text) — but it is silent on other file types (PDFs, binaries), errors, and size limits, which matter for a file-fetching tool with no output 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 front-loaded sentence with zero filler; the most important fact (what it reads) comes first and the return-behavior nuance follows. Efficient, though it could carry one more clause without becoming bloated.

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 one-parameter read tool with full schema coverage and safety annotations, the description covers the essentials plus return-modality behavior. It falls just short of complete by not indicating what happens for non-image, non-text attachments.

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 100% and the single file_id parameter is documented in the schema, including its origin ('Attachment file_id from get_task'). The description adds nothing further about the parameter, so baseline 3 applies.

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 gives a specific verb and resource — 'Read a task attachment' — which no sibling tool does (siblings operate on tasks, boards, projects, comments). It stops short of explicitly contrasting with any sibling, but the resource is unambiguous.

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?

Usage is only implied: an agent can infer it should call this when it needs the contents of an attachment. There is no statement of when not to use it or of prerequisites (e.g., that the file_id must first be obtained via get_task) in the description itself — that hint lives only in the schema.

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