Skip to main content
Glama

approve_project

Approve a completed project to release escrow payments to workers. Call when satisfied with the final delivery.

Instructions

Approve the final delivery of a project.

This triggers release of remaining escrow to all workers. Only call when you're satisfied with the completed work.

Args: project_id: The project ID to approve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual tool handler function for 'approve_project'. It POSTs to /api/projects/{project_id}/approve-final to trigger release of remaining escrow to workers.
    async def approve_project(project_id: int) -> str:
        """Approve the final delivery of a project.
    
        This triggers release of remaining escrow to all workers.
        Only call when you're satisfied with the completed work.
    
        Args:
            project_id: The project ID to approve.
        """
        data = await _post(f"/api/projects/{project_id}/approve-final")
        return json.dumps(data, indent=2)
  • The function signature defines the input schema: project_id is an integer. There is no separate Pydantic model; FastMCP infers the schema from type hints and docstrings.
    async def approve_project(project_id: int) -> str:
  • Registration via the @mcp.tool() decorator on line 92, which registers the function as an MCP tool named 'approve_project'.
    @mcp.tool()
  • Helper function _post() used by approve_project to make the HTTP POST request to the RobotFail API.
    async def _post(path: str, body: dict = None) -> dict:
        async with httpx.AsyncClient(timeout=60) as client:
            r = await client.post(f"{API_BASE}{path}", headers=_headers(), json=body or {})
            r.raise_for_status()
            return r.json()
Behavior4/5

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

The description discloses the key behavioral consequence: 'triggers release of remaining escrow to all workers.' It also implies irreversibility by requiring satisfaction before calling. Without annotations, this is adequate for a simple tool. Missing details on permissions or reversibility, but the core effect is covered.

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?

The description is concise: three sentences and an arg line. Each sentence adds value (purpose, effect, when-to-use). It is front-loaded with the main action. No unnecessary words or repetition.

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 tool with one parameter and an output schema (present but not shown), the description covers the tool's purpose, effect, and usage context. The existence of an output schema means return values need not be explained. The description is complete for an AI agent to decide and invoke correctly.

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 only parameter, project_id, has its role explained: 'The project ID to approve.' While the schema has no descriptions (0% coverage), the description adds meaningful context for the parameter, clarifying its purpose beyond the schema's type/required fields.

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?

Title and description clearly state the action: 'Approve the final delivery of a project.' It specifies the resource (project) and the verb (approve). The description further clarifies that this triggers release of escrow, distinguishing it from project creation or task submission.

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

Usage Guidelines4/5

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

The description explicitly states when to use: 'Only call when you're satisfied with the completed work.' This provides a clear condition. However, it does not mention when not to call or any alternative tools, though from the sibling list, submit_task is likely for submitting work before approval.

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