Skip to main content
Glama

gdex-mcp

by io.github.rpconroy
OverviewDiscussionsAdmin

submit_and_wait_for_request

Submit a subset request and poll its status until it finishes, fails, or timeout_s elapses — instead of calling submit_subset_request and then manually looping on check_request_status. Requires GDEX_TOKEN.

GDEX's API schema doesn't document the exact status vocabulary, so
"finished" is a best-effort match on the status text (words like
"complete" vs. "error"/"fail"). If the outcome comes back "timeout", that
means the request is still pending by our reading, not that it failed —
keep polling with check_request_status(rindex), or re-run this tool with
a longer timeout_s. If it comes back "unknown", the status payload didn't
contain a field we recognize; inspect the raw "status" value yourself.

Args:
    request_json: JSON string of the subsetting request body (see get_control_file_template).
    poll_interval_s: Seconds between status checks (default 15, minimum 5).
    timeout_s: Give up and return the last-seen status after this many seconds (default 600).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeout_sNo
request_jsonYes
poll_interval_sNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and handles it well: it discloses the authentication requirement, the API's undocumented status vocabulary, the best-effort matching semantics, and what 'timeout' and 'unknown' actually mean. This goes well beyond a generic 'submit and poll' statement.

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?

The text is front-loaded with the main purpose and alternative, followed by necessary caveats and a clean Args list. Every sentence adds information; nothing is redundant with the schema.

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?

Given the tool's complexity and the ambiguity in the underlying API's status vocabulary, the description covers authentication, status interpretation, fallback actions, and parameter semantics. The output schema exists, so return-value documentation is not required from the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining each parameter's purpose, default, and constraints: request_json references get_control_file_template, poll_interval_s specifies minimum and default, and timeout_s defines the give-up behavior.

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 names a specific verb and resource ('Submit a subset request and poll its status') and clearly distinguishes itself from the sibling tools submit_subset_request and check_request_status. The core behavior and terminal conditions are stated in the first sentence.

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?

It explicitly tells the agent when to use this tool instead of calling submit_subset_request and manually looping on check_request_status. It also gives concrete follow-up actions for timeout and unknown outcomes, naming the alternative tool to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All gdex-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources