Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Run Data Store Listing

alterlab_store_run

Run a listing with input that matches its input_schema. Reserves the quoted maximum, bills only valid results and refunds the rest. With wait=true (default) it returns results, or a run id with a next_action when the run is still going. Invalid input returns field errors and reserves nothing. Errors carry stable codes such as listing_not_found, listing_degraded, spend_cap_exceeded and blocked_upstream (refunded). Needs an API key with the scrape scope; use alterlab_store_quote first to see the cost.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "alterlab_store_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesListing slug, e.g. from alterlab_store_search
waitNoWait for results (default true); false returns a run id immediately
inputNoInput matching the listing input_schema
versionNoPin a major version, e.g. 1
max_resultsNoMaximum valid results to buy (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the reserve-then-refund billing model, that only valid results are billed, the wait semantics with next_action, that invalid input reserves nothing, and stable error codes including refunded blocked_upstream. It also states the required API key scope, which annotations do not cover.

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?

Dense but front-loaded, leading with the core action and following with billing, wait behavior, and errors in a logical order. Every sentence carries information, though the error-code list is somewhat packed into one clause.

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?

For a mutation tool with a nested input object and no output schema, the description covers billing, refunds, async behavior, error codes, and auth scope. The only gap is that it doesn't describe the shape of successful results, though the absence of an output schema makes that a minor omission.

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 the baseline is 3, but the description adds real meaning: wait=true returns results or a run id with next_action, and max_results is the quoted maximum that is only partially billed. The nested input parameter is clarified as needing to match the listing's input_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?

States a specific verb and resource ('Run a listing') and ties the input to the listing's own input_schema, which distinguishes it from alterlab_store_get and alterlab_store_search. It also names alterlab_store_quote as the cost-preview sibling, though it doesn't contrast with alterlab_run_create or alterlab_batch.

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 directs the agent to call alterlab_store_quote first to see cost, and explains the wait=true default versus wait=false returning a run id. It gives clear context but no explicit when-not-to-use exclusions beyond the quote-first hint.

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

All mcp-server 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