Skip to main content
Glama
Sign In
project-manager

project-manager

by samrullo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pm_get_task

Fetch a task by its ID to view its details including status, assignee, and other properties.

Instructions

GET /tasks/{task_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": {
      "task_id": "<task_id>"
    },
    "name": "pm_get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
x_user_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the HTTP method and path. It does not confirm safety (e.g., read-only), authentication needs, or side effects, leaving the AI agent uninformed.

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

Conciseness2/5

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

The description is extremely concise but at the expense of utility. It consists of a single, minimally informative sentence that does not earn its place because it fails to convey necessary operational details.

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?

Despite the presence of an output schema, the description lacks detail about the tool's response, behavior, and parameters. With no annotations and minimal text, the description is insufficient for an agent to reliably use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not explain any parameters. The two parameters (task_id, x_user_id) are not mentioned or given context, so the description adds no value beyond the schema.

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 description 'GET /tasks/{task_id}' indicates retrieving a specific task via HTTP GET, but it is essentially a restatement of the tool name and does not differentiate it from sibling tools like pm_get_project or pm_get_team.

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?

No guidance is provided on when to use this tool versus alternatives such as pm_list_tasks or pm_update_task. There is no context about prerequisites, use cases, or exclusions.

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

Deploy Server

Other Tools