Skip to main content
Glama

task_get

Retrieve detailed implementation information for a specific project task, including metadata, files to modify, and technical notes, to understand execution requirements.

Instructions

PROJECT MANAGEMENT: Get full details of ONE specific task.

Use this to drill into a single task's implementation details (metadata, files_to_modify, technical_notes). Prefer ticket_get for overview, use this only when you need deep task details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID (e.g., SUBTASK-007-1 or TASK-abc123-1)

Implementation Reference

  • Handler for the task_get tool: fetches the task by ID from the database and returns its JSON-serialized model dump, or an error if not found.
    if name == "task_get":
        task = db.get_task(args["task_id"])
        if not task:
            return f"Task {args['task_id']} not found"
        return _json(task.model_dump())
  • Registration of the task_get tool in the MCP server's list_tools(), defining its name, description, and input schema requiring a task_id.
            Tool(
                name="task_get",
                description="""PROJECT MANAGEMENT: Get full details of ONE specific task.
    
    Use this to drill into a single task's implementation details (metadata, files_to_modify, technical_notes). Prefer ticket_get for overview, use this only when you need deep task details.""",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "task_id": {
                            "type": "string",
                            "description": "Task ID (e.g., SUBTASK-007-1 or TASK-abc123-1)",
                        }
                    },
                    "required": ["task_id"],
                },
            ),
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Get full details'), but doesn't explicitly state behavioral traits like permissions required, error handling, or response format. It adds some context about the type of details returned, but lacks comprehensive behavioral disclosure for a tool with no annotation coverage.

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

Conciseness5/5

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

The description is appropriately sized and front-loaded: the first sentence states the core purpose, and subsequent sentences provide essential usage guidelines without redundancy. Every sentence earns its place by adding distinct value (purpose, details, when to use, alternatives).

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?

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is mostly complete: it covers purpose, usage, and distinguishes from siblings. However, it lacks details on behavioral aspects (e.g., error cases, response structure) that would be helpful since no annotations or output schema exist, leaving minor gaps.

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

Parameters4/5

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

Schema description coverage is 100% for the single parameter (task_id), so the baseline is 3. The description adds value by clarifying the tool's scope ('ONE specific task'), which reinforces the parameter's purpose, but doesn't provide additional semantic details beyond what the schema already documents (e.g., format examples are in the schema).

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?

The description clearly states the tool's purpose with specific verb ('Get full details') and resource ('ONE specific task'), distinguishing it from siblings like task_list (multiple tasks) and ticket_get (overview). It explicitly mentions what details are retrieved: metadata, files_to_modify, technical_notes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool ('only when you need deep task details') and when to use alternatives ('Prefer ticket_get for overview'). It also clarifies the context: 'drill into a single task's implementation details' versus other tools for different purposes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/urjitbhatia/tpm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server