Skip to main content
Glama

list_projects

Retrieve all projects from RobotFail, showing their current status and task counts for easy tracking.

Instructions

List all your projects on RobotFail with their status and task counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler for list_projects. Decorated with @mcp.tool(), it calls the /api/projects endpoint via the _get helper and returns JSON.
    @mcp.tool()
    async def list_projects() -> str:
        """List all your projects on RobotFail with their status and task counts."""
        data = await _get("/api/projects")
        return json.dumps(data, indent=2)
  • The HTTP GET helper used by list_projects to call the RobotFail API.
    async def _get(path: str) -> dict:
        async with httpx.AsyncClient(timeout=30) as client:
            r = await client.get(f"{API_BASE}{path}", headers=_headers())
            r.raise_for_status()
            return r.json()
  • The @mcp.tool() decorator registers list_projects (and all other tool functions) with the FastMCP server. The decorator is applied directly on line 74.
    @mcp.tool()
    async def create_project(description: str, budget_dollars: float) -> str:
        """Submit a new project to RobotFail.
    
        Describe what you need done in the physical world. Be specific about
        location, requirements, and deliverables. The PM engine decomposes it
        into atomic tasks and assigns them to human workers.
    
        Args:
            description: What you need done. Include location, requirements, deliverables.
            budget_dollars: Budget in USD (e.g. 50.00 = $50). Minimum $5.
        """
        data = await _post("/api/projects", {
            "description": description,
            "budget": budget_dollars,
        })
        return json.dumps(data, indent=2)
Behavior4/5

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

No annotations provided, so description carries full burden. It describes a straightforward read-only list operation with status and task counts. Could add more context like authentication or scope, but it's sufficient.

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?

Single, concise sentence that front-loads the key action and resource. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no parameters and an output schema, the description fully covers what the tool does and what it returns.

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?

Input schema has zero parameters and 100% coverage, so description need not add parameter info. Baseline of 4 is appropriate for no-parameter tool.

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?

Clearly states the verb 'List', resource 'projects', and scope 'all your projects' with details on status and task counts. It distinguishes from siblings like 'get_project' which retrieves a single project.

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?

Implies usage when an overview of all projects is needed, but does not explicitly state when not to use it or mention alternatives such as 'get_project' for detailed view of a single project.

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/guinevere-kingsley/robotfail-mcp'

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