Skip to main content
Glama
easydeploy-ai-mcp

easydeploy-ai-mcp

Official

Run batch prediction

run_batch_prediction

Score an entire dataset against a trained model version by starting a batch job; use the returned prediction ID to poll status and download scored results.

Instructions

Score an entire dataset against a trained model version.

Each call starts a new batch job and spends one prediction credit per row; get_prediction follows one already started, by its prediction_id.

Name the model one way: model_version_id for an exact version, or model_id + alias (such as production) for whichever version the alias points to. Prefer the alias for recurring scoring, so the user can promote a new version with set_model_alias without changing the calls; validate a candidate by its model_version_id. The result's modelVersionId is the version that actually scored, and alias echoes the alias that resolved it; report that version next to the output.

project_id and target_feature are auto-resolved from the model version record when omitted. dataset_version_id identifies both the input file and the row count for credit billing (one prediction credit per row).

Holdout validation: score your test dataset version with its labels still in it. The CSV you download via get_prediction is that file in its original row order with every column kept (target and ids included), plus prediction and, for classifiers, one probability_<class> column per class (probability_1 is the positive class for a 0/1 target); compute the holdout metrics and decision threshold yourself from it, since EasyDeploy does not return them. For a string target the probability columns are named by encoded class index (probability_0, probability_1, ... in sorted label order), not by label; the completed prediction's classLabels, from get_prediction, maps each index to its label. Columns the model was not trained on, such as ids, are ignored for scoring and kept in the output, so leave them in to join results back; every training feature must be present or the job fails naming the missing one. The download is capped at 9 MB, so keep test files small enough that their scored output fits, or split the test set across several batches.

Returns immediately by default (fire-and-poll). get_prediction(prediction_id) reports the status; for a completed batch it also has batch_output_available: true, download_url and curl_command. Set wait_for_result=true to block for max_wait_seconds (45 s by default, at most 60 s); if the batch is still running then, the result has timed_out: true and next_steps: poll get_prediction to keep waiting.

Input Schema

NameRequiredDescriptionDefault
aliasNoWith model_id: score with the version this alias (such as 'production') points to when the call runs. Leave empty when passing model_version_id.
model_idNoWith alias: the model whose alias picks the version. Leave empty when passing model_version_id.
project_idNo
target_featureNo
wait_for_resultNo
max_wait_secondsNoWith wait_for_result=true, how long to wait, in seconds (default 45, at most 60; larger values are clamped). Hosts end long tool calls at different times, some at 60 s, so the default returns well before that; poll get_prediction to keep waiting.
model_version_idNoThe exact model version to score with. Leave empty when naming the model by model_id + alias instead.
dataset_version_idYes
poll_interval_secondsNoSeconds between status checks while waiting (default 5.0). Values below 2 are raised to 2.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / properties / alias
      Added value: +{
      +  "default": "",
      +  "description": "With model_id: score with the version this alias (such as 'production') points to when the call runs. Leave empty when passing model_version_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / model_id
      Added value: +{
      +  "default": "",
      +  "description": "With alias: the model whose alias picks the version. Leave empty when passing model_version_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / model_version_id / default
      Added value: +""
    • addedInput schema / properties / model_version_id / description
      Added value: +"The exact model version to score with. Leave empty when naming the model by model_id + alias instead."
    • changedInput schema / required
      Previous value: -[
      -  "model_version_id",
      -  "dataset_version_id"
      -]New value: +[
      +  "dataset_version_id"
      +]
  2. Changed2 schema fields changedv0.4.3
    • changedInput schema / properties / max_wait_seconds / default
      Previous value: -150New value: +45
    • changedInput schema / properties / max_wait_seconds / description
      Previous value: -"With wait_for_result=true, how long to wait, in seconds (default 150). Values above 150 are clamped to 150 so the call returns before MCP hosts end it (about 3 minutes); poll get_prediction to keep waiting."New value: +"With wait_for_result=true, how long to wait, in seconds (default 45, at most 60; larger values are clamped). Hosts end long tool calls at different times, some at 60 s, so the default returns well before that; poll get_prediction to keep waiting."
  3. Changed3 schema fields changedv0.3.0
    • changedInput schema / properties / max_wait_seconds / default
      Previous value: -600New value: +150
    • addedInput schema / properties / max_wait_seconds / description
      Added value: +"With wait_for_result=true, how long to wait, in seconds (default 150). Values above 150 are clamped to 150 so the call returns before MCP hosts end it (about 3 minutes); poll get_prediction to keep waiting."
    • addedInput schema / properties / poll_interval_seconds / description
      Added value: +"Seconds between status checks while waiting (default 5.0). Values below 2 are raised to 2."
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false) by disclosing that every call starts a new job, bills one prediction credit per row, auto-resolves project_id/target_feature, fails naming any missing training feature, clamps waits at 60 s, and returns timed_out plus next_steps on expiry. These are exactly the cost and failure semantics an agent needs before invoking.

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?

Front-loaded with purpose, cost and the polling alternative before the long holdout section, and every paragraph carries real information. It is nonetheless a ~350-word block with redundant restatement of fire-and-poll and some formatting noise (double backticks, a mid-sentence line break), so it is not maximally tight.

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?

For a 9-parameter job-starting tool with an output schema, it covers everything an agent still needs: how the model is named, what the CSV output contains and how columns map back, what is billed, and what happens on timeout. Nothing required to call it correctly is missing.

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 56%, and the description compensates for the bare parameters by explaining the mutually exclusive model-naming modes, the auto-resolution of project_id and target_feature, and dataset_version_id's dual role as input file and billing row count. poll_interval_seconds is left to the schema, which documents it adequately, so this is strong but not exhaustive.

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?

States a specific verb and resource ("Score an entire dataset against a trained model version") and explicitly separates itself from get_prediction ("follows one already started, by its prediction_id"), so an agent can distinguish batch scoring from polling without opening either schema.

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?

Gives concrete routing rules: use model_version_id to validate a candidate, use model_id + alias for recurring scoring so set_model_alias can promote a new version, and use get_prediction instead to follow an existing job. It also names the when-not conditions (holdout files too large for the 9 MB cap should be split across batches).

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