Skip to main content
Glama
crewAIInc

CrewAI Enterprise MCP Server

Official
by crewAIInc

kickoff_crew

Start new CrewAI workflows to automate complex tasks through Claude Desktop. Provides crew IDs for monitoring task progress and results.

Instructions

Start a new crew task

Args:
    inputs: Dictionary containing the query and other input parameters

Returns:
    Dictionary containing the crew task response. The response will contain the crew id which needs to be returned to check the status of the crew.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsYes

Implementation Reference

  • The handler function for the 'kickoff_crew' tool. It sends a POST request to the CrewAI Enterprise server with the provided inputs and returns the JSON response containing the crew task details.
    async def kickoff_crew(inputs: dict[str, Any]) -> dict[str, Any]:
        """Start a new crew task
    
        Args:
            inputs: Dictionary containing the query and other input parameters
    
        Returns:
            Dictionary containing the crew task response. The response will contain the crew id which needs to be returned to check the status of the crew.
        """
        async with httpx.AsyncClient() as client:
            response = await client.post(
                f"{CREWAI_ENTERPRISE_SERVER_URL}/kickoff",
                headers={
                    "Authorization": f"Bearer {CREWAI_ENTERPRISE_BEARER_TOKEN}",
                    "Content-Type": "application/json",
                },
                json={"inputs": inputs},
            )
            response_json = response.json()
            return response_json
  • Registers the 'kickoff_crew' function as an MCP tool using the FastMCP decorator.
    @mcp.tool()
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. It mentions the tool starts a task and returns a crew id for status checking, but doesn't address critical behavioral aspects like whether this is a synchronous or asynchronous operation, what happens if a task fails, or any permission/rate limit requirements.

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 appropriately concise with three sentences that each serve a purpose: stating the action, describing the input, and explaining the output. However, the structure could be improved by front-loading more critical information about the tool's behavior.

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 a complex nested parameter with 0% schema coverage, the description is inadequate. It doesn't explain what constitutes valid 'inputs', what the response structure looks like beyond containing a crew id, or the operational characteristics of starting a crew task.

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

Parameters2/5

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

With 0% schema description coverage and 1 parameter that's a nested object, the description only vaguely mentions 'Dictionary containing the query and other input parameters.' This provides minimal semantic value beyond what the bare schema indicates, failing to compensate for the complete lack of schema documentation.

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 verb ('Start') and resource ('new crew task'), providing a specific purpose. However, it doesn't distinguish this tool from its sibling 'get_crew_status' beyond the obvious difference in action.

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

Usage Guidelines3/5

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

The description implies usage context by mentioning that the returned crew id is needed to check status with 'get_crew_status', suggesting a workflow relationship. However, it doesn't explicitly state when to use this tool versus alternatives or provide any exclusions.

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