Skip to main content
Glama

get_run_status

Check the status of a BitScale Grid enrichment run using the request ID from run_grid. Poll every 2-5 seconds to monitor progress until completion or failure.

Instructions

Check the status of a previously triggered Grid run.

Use this after run_grid returns a request_id (either from async mode or when sync mode times out after 120 seconds).

Poll every 2-5 seconds until status is "completed" or "failed". Avoid polling more frequently as requests count toward the rate limit (5 req/sec per workspace).

Args: request_id: The request_id UUID returned by run_grid.

Returns: {mode, status, grid_id, outputs (when completed)}. Status is one of: "running", "completed", or "failed". When completed, outputs contains {column_id: {value, name}} for each enriched column.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:237-260 (handler)
    The get_run_status tool is defined and implemented here, decorated with @mcp.tool(). It validates the request_id and makes a request to the /run/status/ endpoint.
    @mcp.tool()
    def get_run_status(request_id: str) -> str:
        """
        Check the status of a previously triggered Grid run.
    
        Use this after run_grid returns a request_id (either from async mode or
        when sync mode times out after 120 seconds).
    
        Poll every 2-5 seconds until status is "completed" or "failed".
        Avoid polling more frequently as requests count toward the rate limit
        (5 req/sec per workspace).
    
        Args:
            request_id: The request_id UUID returned by run_grid.
    
        Returns: {mode, status, grid_id, outputs (when completed)}.
        Status is one of: "running", "completed", or "failed".
        When completed, outputs contains {column_id: {value, name}} for each
        enriched column.
        """
        if not request_id:
            raise ValueError("request_id must not be empty")
        data = _get(f"/run/status/{request_id}")
        return json.dumps(data, indent=2)
Behavior5/5

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

No annotations provided, but description fully compensates by disclosing: sync timeout (120s), rate limits, status lifecycle ('running'→'completed'/'failed'), and conditional output availability.

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?

Well-structured with Args/Returns sections. Front-loaded purpose. Slightly verbose in describing return values which may be redundant with existing output schema, but justified by conditional logic explanations.

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?

Comprehensive for an async polling tool: covers trigger condition, polling strategy, rate limiting, and output structure. With output schema present, description appropriately focuses on behavioral workflow rather than just return types.

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?

Schema coverage is 0% (request_id lacks description), but description compensates by specifying it is a 'UUID' and its provenance ('returned by run_grid'), clarifying semantics beyond raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'Check' and resource 'Grid run' with explicit scope 'previously triggered' distinguishing it from run_grid. However, could more explicitly differentiate from sibling get_grid_details.

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

Usage Guidelines5/5

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

Explicitly states when to use ('after run_grid returns a request_id'), provides concrete polling interval (2-5 seconds), and warns against excessive polling due to rate limits (5 req/sec).

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/featherflow/bitscale-mcp'

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