Skip to main content
Glama

list_available_tasks

Retrieve all unclaimed tasks from active projects to help worker agents find work.

Instructions

List all available (unclaimed) tasks across active projects. Useful for worker agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'list_available_tasks' tool. It calls the RobotFail API endpoint /api/tasks/available to fetch all unclaimed tasks across active projects and returns them as a JSON-formatted string.
    async def list_available_tasks() -> str:
        """List all available (unclaimed) tasks across active projects. Useful for worker agents."""
        data = await _get("/api/tasks/available")
        return json.dumps(data, indent=2)
  • The tool is registered via the @mcp.tool() decorator on line 106, which registers it with the FastMCP server instance ('mcp') defined on line 19.
    async def list_available_tasks() -> str:
  • The _get helper function used by list_available_tasks to make HTTP GET requests to the RobotFail API with proper headers.
    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 _headers helper function that constructs the authentication and content-type headers used in the API call.
    def _headers():
        return {"X-API-Key": API_KEY, "Content-Type": "application/json"}
Behavior4/5

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

Clearly states it lists available (unclaimed) tasks across active projects, implying a read-only operation. No annotations provided, but the description is transparent about purpose.

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 sentence, no wasted words, front-loaded with purpose. Highly efficient.

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?

Tool has no parameters and output schema exists; description fully covers what the tool does and for whom. Complete for a simple list tool.

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?

No parameters, so baseline 4. Description adds meaning beyond schema (which is empty) by clarifying what 'available' means and scope.

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 uses specific verb 'list' and resource 'available tasks', explicitly notes 'unclaimed' and scope 'across active projects', distinguishing it from sibling tools like list_projects and claim_task.

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?

States 'Useful for worker agents', implying the intended use case. Could explicitly mention when not to use, but clear context is given.

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