Skip to main content
Glama
chipocrudos

Tasks MCP Server

by chipocrudos
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_tasks_status

Retrieve current task status values from the Tasks MCP Server to monitor progress and manage workflow efficiently.

Instructions

Get the status tasks values. Returns: dict: The status tasks values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/tasks.py:136-143 (handler)
    The handler function implementing the logic for the 'get_tasks_status' tool. It returns a dictionary of all TaskStatus enum names mapped to their integer values.
    @mcp.tool()
async def get_tasks_status() -> dict:
    """Get the status tasks values.
    Returns:
        dict: The status tasks values.
    """
    return {status.name: status.value for status in TaskStatus}
  • src/config/server.py:35-35 (registration)
    The call to create_tasks_tools(mcp) which defines and registers the get_tasks_status tool (along with other tasks tools) on the FastMCP server instance.
    create_tasks_tools(mcp)
  • src/models/tasks.py:6-10 (helper)
    The TaskStatus IntEnum used by the get_tasks_status tool to generate its output dictionary of status values.
    class TaskStatus(IntEnum):
    CREATED = 0
    IN_PROGRESS = 1
    COMPLETED = 2

Tool Definition Quality

C2/5.0
Behavior1/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 of behavioral disclosure. The description only states it returns a dictionary of status tasks values, without explaining what 'status tasks values' means, whether this is a read-only operation, what permissions might be required, or any other behavioral characteristics. This leaves the agent with insufficient information about how the tool behaves.

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?

The description is brief with two sentences, but the first sentence is tautological and adds little value. The second sentence about the return type is useful but could be more informative. While appropriately sized, the content isn't front-loaded with meaningful information that helps the agent understand the tool's purpose.

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?

Given the complexity of having multiple sibling tools with similar names and no annotations or output schema, the description is incomplete. It doesn't clarify what differentiates this tool from 'get_task_tool' or 'tasks_list_tool', nor does it explain what 'status tasks values' means in context. For a tool with 0 parameters but potentially important distinctions from siblings, more context is needed.

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?

The tool has 0 parameters, and schema description coverage is 100%. With no parameters to document, the description doesn't need to provide parameter semantics. The baseline for 0 parameters is 4, as there's nothing for the description to compensate for regarding parameters.

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

Purpose2/5

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

The description states 'Get the status tasks values' which is a tautology that essentially restates the tool name 'get_tasks_status'. It doesn't provide a clear, specific verb+resource combination or distinguish this tool from its siblings like 'get_task_tool' or 'tasks_list_tool'. The description is vague about what exactly 'status tasks values' means.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus its siblings. With tools like 'get_task_tool', 'tasks_list_tool', and 'filter_tasks_tool' available, there's no indication whether this tool retrieves all task statuses, aggregated status values, or something else. No context, exclusions, or alternatives are mentioned.

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/chipocrudos/tasks-mcp'

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