Skip to main content
Glama
crewAIInc

CrewAI Enterprise MCP Server

Official
by crewAIInc

get_crew_status

Check the status of deployed CrewAI workflows by providing a crew task ID to monitor progress and results.

Instructions

Get the status of a crew task

Args:
    crew_id: The ID of the crew task to check

Returns:
    Dictionary containing the crew task status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crew_idYes

Implementation Reference

  • The main handler function for the 'get_crew_status' MCP tool. It is registered via the @mcp.tool() decorator and implements the logic to fetch crew status via HTTP GET request to the CrewAI Enterprise server using the provided crew_id.
    @mcp.tool()
    async def get_crew_status(crew_id: str) -> dict[str, Any]:
        """Get the status of a crew task
    
        Args:
            crew_id: The ID of the crew task to check
    
        Returns:
            Dictionary containing the crew task status
        """
        async with httpx.AsyncClient() as client:
            response = await client.get(
                f"{CREWAI_ENTERPRISE_SERVER_URL}/status/{crew_id}",
                headers={
                    "Authorization": f"Bearer {CREWAI_ENTERPRISE_BEARER_TOKEN}",
                    "Content-Type": "application/json",
                },
            )
            return response.json()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this is a read operation ('Get'), it doesn't address important behavioral aspects like whether this requires authentication, rate limits, error conditions, or what specific status values might be returned. The description provides minimal behavioral context beyond the basic operation.

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?

The description is well-structured with clear sections for Args and Returns, and every sentence serves a purpose. It's appropriately sized for a single-parameter tool, though the 'Dictionary containing the crew task status' return description could be more specific about what the dictionary contains.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficiently complete. While it covers the basic operation and parameter, it lacks crucial information about authentication requirements, error handling, status format/details, and relationship to the sibling tool that would help the agent use it effectively.

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?

The description explicitly documents the single parameter 'crew_id' and its purpose ('The ID of the crew task to check'), which adds meaningful context beyond the schema's 0% description coverage. However, it doesn't provide format details, examples, or constraints for the crew_id parameter that would be helpful for the agent.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('status of a crew task'), making it immediately understandable. However, it doesn't explicitly differentiate from its sibling tool 'kickoff_crew', which appears to be a different operation (initiating vs. checking status).

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 description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, timing considerations, or relationship to the sibling 'kickoff_crew' tool, leaving the agent without context for appropriate selection.

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/crewAIInc/enterprise-mcp-server'

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