Skip to main content
Glama

Get a task

get_task
Read-onlyIdempotent

One task of list_tasks by id.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the task

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
archivedNo
billable_by_defaultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds essentially nothing on top: no statement about what happens with a missing or foreign id, whether access is scoped to the caller's workspace, or any return-shape nuance. With the bar lowered by annotations, this still contributes almost no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no wasted wording, but the single sentence fragment is under-structured rather than concise: no leading verb, and the key differentiator (single task vs. list) is buried in a prepositional phrase. Front-loading the verb and the id requirement would cost no extra words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one uuid param, output schema present, annotations covering safety), so much is carried by structured fields. Still, the description leaves the agent without the one thing it cannot infer: whether an id must come from list_tasks and how a not-found or out-of-scope id behaves.

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 there is a single required uuid parameter already described as 'The id of the task'. The description's 'by `id`' merely echoes that field, adding no format, sourcing, or constraint detail. Baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'One task of list_tasks by `id`' does convey that this retrieves a single task, as opposed to the collection returned by list_tasks, and the id key hints at lookup. But it is phrased as a noun phrase with no verb, and 'of list_tasks' is ambiguous (is it a member of the list result, or the same dataset?). An agent can guess the intent, but it is not stated cleanly.

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?

The reference to list_tasks implies a single-vs-collection split, but there is no explicit 'use this when you already have an id' or 'use list_tasks to discover ids first'. No prerequisites, no error-path guidance (e.g., unknown id), and no mention of the other get_* siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources