Skip to main content
Glama

fal-get-status

Retrieve the execution status of a model by supplying request ID and model ID, enabling follow-up with the result retrieval tool.

Instructions

Get the status of a model. The status is returned using the fal.run endpoint. You need to check the status of the model using the fal-get-status tool, then get the result using the fal-get-result tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYes
modelIdYes

Implementation Reference

  • The tool registration and handler for 'fal-get-status'. It defines the tool with schema parameters (requestId: z.string(), modelId: z.string()) and the handler that calls client.getStatus(requestId, modelId) to fetch the async job status.
    server.tool(
        'fal-get-status',
        'Get the status of a model. The status is returned using the fal.run endpoint. You need to check the status of the model using the fal-get-status tool, then get the result using the fal-get-result tool.',
        { requestId: z.string(), modelId: z.string() },
        async ({ requestId, modelId }) => {
            const output = await client.getStatus(requestId, modelId);
            return { content: [{ type: 'text', text: toText(output) }] };
        },
    );
  • The getStatus() method on FalClient that constructs the URL to the fal.ai queue status endpoint and performs the actual HTTP GET request to retrieve the job status.
    async getStatus(requestId: string, modelId: string): Promise<unknown> {
        const baseModel = this._baseModelId(this._normalizeModelId(modelId));
        const url = `${this.QUEUE_BASE}/${baseModel}/requests/${encodeURIComponent(requestId)}/status`;
        return await this._getJson(url);
    }
  • The tool is registered via server.tool('fal-get-status', ...) inside the registerTools function, which is exported and called from the server startup code.
    server.tool(
        'fal-get-status',
        'Get the status of a model. The status is returned using the fal.run endpoint. You need to check the status of the model using the fal-get-status tool, then get the result using the fal-get-result tool.',
        { requestId: z.string(), modelId: z.string() },
        async ({ requestId, modelId }) => {
            const output = await client.getStatus(requestId, modelId);
            return { content: [{ type: 'text', text: toText(output) }] };
        },
    );
  • The input schema for fal-get-status defines two required string parameters: requestId and modelId, validated using Zod.
    { requestId: z.string(), modelId: z.string() },
Behavior2/5

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

No annotations exist, and the description provides minimal behavioral detail (only that status is returned via fal.run endpoint). Does not disclose read-only nature, error handling, or response format.

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?

Two concise sentences: one for purpose, one for workflow. Could be more structured but is efficient and front-loaded.

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?

Given 2 params, no output schema, and no annotations, the description provides the essential workflow link to fal-get-result but lacks details on status values, error conditions, or parameter origin.

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 description coverage is 0%, and the description does not explain the purpose or format of requestId and modelId beyond their names.

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?

Clearly states the tool gets the status of a model and distinguishes it from fal-get-result by indicating the workflow order.

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?

Explicitly instructs to use this tool before fal-get-result, providing a clear workflow. However, no mention of when not to use or alternatives.

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/Forge-Systems-Hub/mcp-fal-ai-server'

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