Skip to main content
Glama

get_project

Retrieve detailed project information including tasks, workers, and escrow state by providing a project ID.

Instructions

Get detailed info about a specific project including all tasks, workers, and escrow state.

Args: project_id: The project ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_project tool handler function — fetches detailed info about a specific project via a GET request to /api/projects/{project_id}.
    @mcp.tool()
    async def get_project(project_id: int) -> str:
        """Get detailed info about a specific project including all tasks, workers, and escrow state.
    
        Args:
            project_id: The project ID.
        """
        data = await _get(f"/api/projects/{project_id}")
        return json.dumps(data, indent=2)
  • The tool is registered via the @mcp.tool() decorator from FastMCP.
    @mcp.tool()
  • The _get helper function that get_project relies on to make the HTTP GET request to 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()
Behavior2/5

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

With no annotations provided, description carries full burden but does not disclose read-only nature, authentication needs, or side effects. The action 'Get' implies read-only, but explicit statement would be better.

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?

Single sentence with bullet-like args is concise. Could integrate arg description more naturally, but no extraneous text.

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

Completeness3/5

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

Output schema exists, so return values are covered. However, missing context like 'use after list_projects to get an ID' or prerequisites. Adequate for a simple retrieval but incomplete for workflow orchestration.

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?

Schema coverage is 0%; description only repeats parameter name 'project_id' without adding formatting, source, or example. For a single integer, minimal burden but still fails to add value.

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?

Description clearly states 'Get detailed info about a specific project' and enumerates included data (tasks, workers, escrow state). This distinguishes it from siblings like list_projects (which lists projects) and approve_project (which modifies state).

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?

No guidance on when to use this tool versus siblings like list_projects, or on prerequisites such as needing a project ID. No mention of typical workflow steps.

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