Skip to main content
Glama
Arkava-AI
by Arkava-AI

Get Generation Status

gamma_get_status
Read-onlyIdempotent

Check the status of a Gamma generation. Returns URL and title once completed.

Instructions

Check the status of a Gamma generation.

Use this tool to check if a previously started generation has completed. Generations typically take 30 seconds to 2 minutes depending on complexity.

PARAMETERS:

  • generationId (required): The ID returned from gamma_generate

  • waitForCompletion: If true, polls until complete (max 5 minutes)

RETURNS:

  • status: pending, completed, or failed

  • url: Link to view content (when completed)

  • title: Content title

  • creditsUsed: Credits consumed

EXAMPLE: { generationId: "gen_abc123", waitForCompletion: true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
generationIdYesThe generation ID returned from gamma_generate
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
waitForCompletionNoIf true, poll until generation completes (up to 5 minutes). If false, return current status immediately.
Behavior4/5

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

Annotations already provide read-only, idempotent, non-destructive hints. Description adds polling behavior and return values, enhancing transparency beyond annotations.

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?

Well-structured with purpose, usage, parameters, returns, example. Every sentence contributes, no fluff.

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?

Comprehensive for a status-checking tool: covers all parameters, behavior, return values, and example. No gaps given absence of output schema.

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 100% so baseline is 3. Description adds context on polling mechanism and example usage, adding value over schema alone.

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 clearly states 'Check the status of a Gamma generation' with specific verb and resource, distinguishes from siblings like gamma_generate by focusing on status polling.

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 says 'Use this tool to check if a previously started generation has completed', providing clear context. Could mention when not to use, but example and sibling differentiation suffice.

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/Arkava-AI/gamma-mcp-server'

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