Skip to main content
Glama

health

Check RobotFail platform health and view stats on projects, tasks, and workers.

Instructions

Check RobotFail platform health and stats — projects, tasks, workers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'health' tool is registered via the @mcp.tool() decorator on line 48.
    @mcp.tool()
    async def health() -> str:
        """Check RobotFail platform health and stats — projects, tasks, workers."""
        data = await _get("/api/health")
        return json.dumps(data, indent=2)
  • The health() async function executes the tool logic: calls _get('/api/health') and returns JSON.
    @mcp.tool()
    async def health() -> str:
        """Check RobotFail platform health and stats — projects, tasks, workers."""
        data = await _get("/api/health")
        return json.dumps(data, indent=2)
  • The _get() helper function used by health() to make HTTP GET requests 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, the description must disclose behavior. It only says 'Check' implying read-only, but lacks details on data freshness, rate limits, or what constitutes health. Minimal behavioral context provided.

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?

A single sentence of 10 words with no wasted content. Efficiently conveys the tool's purpose.

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

Completeness4/5

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

Given no parameters and the presence of an output schema, the description need not explain return values. However, it could hint at the structure of the output. Still, it is adequate for a simple health check.

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?

There are no parameters, and schema coverage is 100%. Baseline for zero parameters is 4, as the description does not need to add parameter meaning.

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?

The description clearly states the verb 'Check' and the resource 'RobotFail platform health and stats — projects, tasks, workers.' It distinguishes from sibling tools, which are specific CRUD and task operations.

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 for checking overall status, but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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