Skip to main content
Glama

Estimate a job's price (free, books nothing)

estimateExecution
Read-onlyIdempotent

Symbioza price, cost, feasibility, balance or credit: ALWAYS call the tool (estimateExecution for a price), never answer from memory, prior chat, arithmetic or cached values, never replace its price card with prose, never invent a total. Never make the user pick a budget just to see the likely cost: estimate without budgetUsd, explain the estimate, then ask for the spending approval. Call estimateExecution once per spec and budget: the answer already has the price, runtime, readiness and balance; call again only when the spec or budget changes. Symbioza selects compatible compute internally and returns estimate, shown first: status best_effort with likelyUsd, lowUsd–highUsd, confidence, runtime (the expected runtime) and costBreakdown, or rate_only with only perHourUsd; then price (evidence, summary, perHourUsd, includes, unknown, nextStep), estimatedPriceUsd (only when price.evidence is customer, then equal to estimate.likelyUsd), readiness (preliminary while a budget or saved access is missing — budget_required, access_required — else ready; inputs_unverified and inputs_not_declared are advice that never blocks a submit) and runtime (boundSeconds, boundBy, note): only where the run would be stopped — a limit, never a prediction. A maxRuntimeSeconds above 172800 (48 hours) is refused here too, with invalid_spec, as submitJob refuses it. No matching machine: a refusal in submitJob's shape — reason, code no_compute, action relax_spec_or_retry; still free and still books nothing. image must be one of the images we have verified launch on our machines: pytorch/pytorch:2.4.1-cuda12.1-cudnn9-runtime, pytorch/pytorch:2.4.0-cuda12.1-cudnn9-runtime, tensorflow/tensorflow:2.15.0. Any other image is refused with code invalid_spec, action fix_spec and a supportedImages list, before anything is booked or charged. budgetUsd is what you are willing to spend on the job, and you are never billed more than that. Every dollar figure returned by any tool here is in that same unit: what you pay. It also returns account: availableUsd (what this account can spend right now, promotional credit included), promoUsd and promoExpiresAtMs, promoJobCapUsd (the most promotional credit any one job may use — a larger budget needs paid balance for the rest), coversThisJob (would submitJob accept this spec's budget today; null when the spec has no budgetUsd), claimableUsd (free compute credit this account could still take, or null), nextAction ("add_funds" or "claim_credit", null when the job is already covered), claimUrl, and with a budget topupUrl and shortfallUsd (the whole dollars of credit this job still needs, 0 when covered; topupUrl carries it — give the user that link as returned). When the spec attaches secrets, it also returns access: ready (the saved sets that will be injected: name, type and variable names), required (each missing, ambiguous or type_mismatch reference — a missing one with a setupUrl to give the user, an ambiguous one with candidates to ask about), conflicts, complete and nextAction (add_access or fix_spec); submitJob refuses until access.complete is true. A warning env_may_hold_credential names env variables that look like credentials — move them to saved Secrets. It also returns specDigest, a fingerprint of the exact spec and budget priced here — only when the spec carries budgetUsd, since submitJob refuses one without it: pass it to submitJob and a spec or budget changed since this estimate is refused with invalid_spec instead of run. estimate.runtime is the one runtime story: how long this job likely runs (likelySeconds, its range and one evidence sentence); runtime.boundSeconds is only where the run would be stopped — a limit, never a prediction. When estimate.status is best_effort, show estimate.likelyUsd with its range (lowUsd–highUsd), the expected runtime, confidence, costBreakdown and disclaimer — a best-effort estimate from the strongest evidence about this workload; it is not a quote, and image history alone is never evidence about this job. When estimate.status is rate_only, nothing predicts the runtime: tell the user there is no total, and give price.perHourUsd (what each hour of running costs). estimatedPriceUsd is returned only when price.evidence is customer — the estimate priced at the user's own maxRuntimeSeconds — and then equals estimate.likelyUsd. No range is given without evidence for one. budgetUsd stays the hard maximum either way, and is never needed to see an estimate. Read the account before submitJob so a funding problem is something you fix rather than something you discover from a refusal — claiming credit needs no payment. Declare datasetGb as the total data the box will ingest, including data it downloads itself, so a host too slow to pull it in time is filtered before booking. Declare gpu.minCudaVersion (e.g. 13.0) if your image pins a CUDA build — it filters the market here too, so the price you get back is for a host that can actually run your image. Only when the user explicitly requires a particular model for their own benchmark, declare gpu.gpuNameExact: true with gpu.gpuName to price only that exact card model, with every substitute refused — the price then reflects the instrument a measurement actually needs. Add gpu.minPowerLimitW to price only boards at or above that TDP, since one model name covers several. May also return advisory warnings/notes (additive, may be absent) — e.g. ingest_may_exceed_deadline when the declared datasetGb cannot move inside maxRuntimeSeconds over the link the selected host advertises (or the rate we measured on that box before), and ingest_not_predicted when that host publishes no link speed and we have never measured one. Advisory ONLY: it never refuses and never changes the ranking or price; it is about the box we would book for you, not about your data's source, whose speed we do not measure from here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specYesThe job spec to estimate: image + command run on a rented box sized by minDiskGb (and gpu, when declared). budgetUsd is optional here — leave it out to see the likely cost before the user chooses one; submitJob requires it. Supply the workload: the image, the command, its inputs, the expected outputs and budgetUsd. Symbioza sizes the machine — do not ask the user to choose CPU cores, RAM, VRAM, a GPU model, a provider or a region, and do not derive a resource minimum from a thread count, a worker count or a measurement taken somewhere else. gpu.minVramGb, minRamGb and minCpuCores are optional expert floors: declare one only when the workload has evidence for it, and omit it otherwise — an omitted floor is sized by Symbioza, never treated as zero. The gpu block is optional: leave it out and the job is still GPU work with Symbioza sizing the card; declare it to carry minCudaVersion or an evidenced floor.
authKeyNoUsually omit this. The customer door — the OAuth-signed-in HTTPS connector at https://symbioza.dev/mcp — authenticates the session itself, so no key is passed per call. Only a self-hosted or test transport passes a key here.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoMachine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, access_required, secret_conflict, no_compute, unavailable, refused
notesNoAdvisory only, never a refusal
priceNoWhat the price rests on, what it includes and what is still unknown
accessNoThe saved secrets this spec attaches, by name and type only
actionNoThe one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, add_access, relax_spec_or_retry, retry_later, contact_support
reasonNoWhy, in a customer-safe sentence
accountNoThis account's spending position for the spec
runtimeNoboundSeconds, boundBy (budget | customer | platform), note: where the run would be STOPPED on that machine — a limit, never a prediction. The expected runtime is estimate.runtime
estimateNoThe best-effort estimate of the total bill: show likelyUsd with its range, confidence and disclaimer, or perHourUsd when rate_only. budgetUsd stays the hard cap
rejectedNoPresent and true when the call was refused; nothing was booked or charged
warningsNoAdvisory only, never a refusal
budgetUsdNoYour own cap, read back; nothing bills past it. Absent when the spec has none
readinessNoWhat stands between this estimate and a submittable one, plus advice about its inputs
provenanceNo
specDigestNoFingerprint of the exact spec and budget priced here; pass it to submitJob. Absent when the spec has no budgetUsd: submitJob requires one
supportedImagesNoOn an unverified-image refusal: the images the door accepts
estimatedPriceUsdNoWhat this spec is expected to bill you, in dollars — present only when price.evidence is customer (the estimate priced at your own maxRuntimeSeconds), and then equal to estimate.likelyUsd; otherwise absent and the total is estimate.likelyUsd

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / spec / properties / pinHost / description
      Previous value: -"Set true for a measurement/benchmark workload whose numbers are only comparable on one machine. The job then FAILS if its box is lost mid-run instead of being rerouted to a different one — a silent host swap would make the results meaningless. Default false: a lost box may be replaced by another machine."New value: +"Accepted for compatibility and ignored. A machine that is lost or never starts may be replaced by another one, inside budgetUsd. To keep a benchmark on one GPU model, set gpu.gpuName with gpu.gpuNameExact."
  2. Changed2 schema fields changed
    • changedOutput schema / properties / estimatedPriceUsd / description
      Previous value: -"What this spec is expected to bill you, in dollars — present only when price.evidence is customer (priced at your own maxRuntimeSeconds); absent when nothing about this job predicts its runtime"New value: +"What this spec is expected to bill you, in dollars — present only when price.evidence is customer (the estimate priced at your own maxRuntimeSeconds), and then equal to estimate.likelyUsd; otherwise absent and the total is estimate.likelyUsd"
    • changedOutput schema / properties / runtime / description
      Previous value: -"basis, referenceSeconds, boundSeconds, boundBy, note: the runtime the estimate assumes and where the run would be stopped"New value: +"boundSeconds, boundBy (budget | customer | platform), note: where the run would be STOPPED on that machine — a limit, never a prediction. The expected runtime is estimate.runtime"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / estimate
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "The best-effort estimate of the total bill: show likelyUsd with its range, confidence and disclaimer, or perHourUsd when rate_only. budgetUsd stays the hard cap",
      +  "properties": {
      +    "assumptions": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "confidence": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "low | medium | high — how strong the runtime evidence is; null when rate_only"
      +    },
      +    "costBreakdown": {
      +      "description": "The likely total line by line, in the bill's own categories; the lines sum to likelyUsd",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "label": {
      +            "type": "string"
      +          },
      +          "usd": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "category",
      +          "label",
      +          "usd"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "disclaimer": {
      +      "description": "Show it with the figures: best-effort, may differ, budgetUsd is the hard maximum",
      +      "type": "string"
      +    },
      +    "highUsd": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The range the charge likely falls in; never above budgetUsd"
      +    },
      +    "likelyUsd": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The likely total charge for a run that works, in dollars; a best-effort estimate, never a quote. null when rate_only"
      +    },
      +    "limitedBySpendingLimit": {
      +      "description": "true when the top of the range is budgetUsd itself: the run is stopped there and billed no more",
      +      "type": "boolean"
      +    },
      +    "lowUsd": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "perHourUsd": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "What each hour of running costs on the machine Symbioza would book"
      +    },
      +    "runtime": {
      +      "additionalProperties": {},
      +      "description": "likelySeconds, lowSeconds, highSeconds, basis (same-workload | workload-family | command-heuristic | platform-history | customer-cap | none), evidence (one sentence for the user), samples",
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "status": {
      +      "description": "best_effort: likelyUsd/lowUsd/highUsd are set | rate_only: nothing predicts the runtime, so there is no total — show perHourUsd",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "likelyUsd",
      +    "lowUsd",
      +    "highUsd",
      +    "confidence",
      +    "perHourUsd",
      +    "runtime",
      +    "costBreakdown",
      +    "limitedBySpendingLimit",
      +    "assumptions",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / price / properties / evidence / description
      Previous value: -"customer: priced at your own maxRuntimeSeconds | insufficient: nothing about this job predicts its runtime, so this is not a quote"New value: +"customer: priced at your own maxRuntimeSeconds | best-effort: a likely total and range in estimate, not a quote | insufficient: nothing about this job predicts its runtime, so only the hourly price"
  4. Changed1 schema field changed
    • changedInput schema / properties / spec / properties / gpu / properties / count / description
      Previous value: -"GPUs on ONE machine. Must be 1 — a higher count is REFUSED, never silently reduced to one card. Omit it."New value: +"Exact number of GPUs on ONE machine (never N separate machines). Omit it for one GPU, or declare 2; any other count is REFUSED, never silently changed. Declare it only when the workload runs that many processes on a single host (for example torchrun --nproc_per_node=N); minVramGb then applies to each GPU."
  5. Changed3 schema fields changed
    • changedInput schema / properties / spec / properties / gpu / properties / count / description
      Previous value: -"GPUs on ONE machine. Must be 1 — a higher count is REFUSED, never silently reduced to one card. Omit it unless you mean several cards on a single host (that is not N separate machines)."New value: +"GPUs on ONE machine. Must be 1 — a higher count is REFUSED, never silently reduced to one card. Omit it."
    • changedInput schema / properties / spec / properties / gpu / properties / count / maximum
      Previous value: -9007199254740991New value: +16
    • changedInput schema / properties / spec / properties / gpu / properties / minVramGb / description
      Previous value: -"Optional. A VRAM floor the box must meet, only when the workload has an evidenced one (a measured peak, a known model footprint). Omit it when unknown: Symbioza then sizes the GPU itself. Never ask the user to choose a tier, and never derive a number from an unrelated run."New value: +"Optional. A VRAM floor the box must meet, PER GPU, only when the workload has an evidenced one (a measured peak, a known model footprint). Omit it when unknown: Symbioza then sizes the GPU itself. Never ask the user to choose a tier, and never derive a number from an unrelated run."
  6. Changed14 schema fields changed
    • changedInput schema / properties / spec / description
      Previous value: -"The job spec: image + command run on a rented box sized by minDiskGb (and gpu, when declared), under budgetUsd. Supply the workload: the image, the command, its inputs, the expected outputs and budgetUsd. Symbioza sizes the machine — do not ask the user to choose CPU cores, RAM, VRAM, a GPU model, a provider or a region, and do not derive a resource minimum from a thread count, a worker count or a measurement taken somewhere else. gpu.minVramGb, minRamGb and minCpuCores are optional expert floors: declare one only when the workload has evidence for it, and omit it otherwise — an omitted floor is sized by Symbioza, never treated as zero. The gpu block is optional: leave it out and the job is still GPU work with Symbioza sizing the card; declare it to carry minCudaVersion or an evidenced floor."New value: +"The job spec to estimate: image + command run on a rented box sized by minDiskGb (and gpu, when declared). budgetUsd is optional here — leave it out to see the likely cost before the user chooses one; submitJob requires it. Supply the workload: the image, the command, its inputs, the expected outputs and budgetUsd. Symbioza sizes the machine — do not ask the user to choose CPU cores, RAM, VRAM, a GPU model, a provider or a region, and do not derive a resource minimum from a thread count, a worker count or a measurement taken somewhere else. gpu.minVramGb, minRamGb and minCpuCores are optional expert floors: declare one only when the workload has evidence for it, and omit it otherwise — an omitted floor is sized by Symbioza, never treated as zero. The gpu block is optional: leave it out and the job is still GPU work with Symbioza sizing the card; declare it to carry minCudaVersion or an evidenced floor."
    • changedInput schema / properties / spec / properties / budgetUsd / description
      Previous value: -"Hard spend ceiling for the whole job, USD. The job is refused or stopped rather than exceeding it."New value: +"Optional here: the job's hard spend ceiling, USD. Leave it out to see the estimate before the user chooses one; submitJob requires it, so estimate again with the user's budget before submitting."
    • changedInput schema / properties / spec / required
      Previous value: -[
      -  "image",
      -  "command",
      -  "budgetUsd"
      -]New value: +[
      +  "image",
      +  "command"
      +]
    • addedOutput schema / properties / account / properties / coversThisJob / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / account / properties / coversThisJob / description
      Added value: +"Would submitJob accept this spec's budget today; null when the spec has no budgetUsd"
    • removedOutput schema / properties / account / properties / coversThisJob / type
      Removed value: -"boolean"
    • addedOutput schema / properties / account / properties / topupUrl / description
      Added value: +"With a budget: the link for the credit this job needs"
    • changedOutput schema / properties / account / required
      Previous value: -[
      -  "availableUsd",
      -  "promoUsd",
      -  "promoExpiresAtMs",
      -  "coversThisJob",
      -  "promoJobCapUsd",
      -  "claimableUsd",
      -  "nextAction",
      -  "claimUrl",
      -  "topupUrl"
      -]New value: +[
      +  "availableUsd",
      +  "promoUsd",
      +  "promoExpiresAtMs",
      +  "coversThisJob",
      +  "promoJobCapUsd",
      +  "claimableUsd",
      +  "nextAction",
      +  "claimUrl"
      +]
    • changedOutput schema / properties / budgetUsd / description
      Previous value: -"Your own cap, read back; nothing bills past it"New value: +"Your own cap, read back; nothing bills past it. Absent when the spec has none"
    • changedOutput schema / properties / estimatedPriceUsd / description
      Previous value: -"What this spec is expected to bill you, in dollars"New value: +"What this spec is expected to bill you, in dollars — present only when price.evidence is customer (priced at your own maxRuntimeSeconds); absent when nothing about this job predicts its runtime"
    • addedOutput schema / properties / price
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "What the price rests on, what it includes and what is still unknown",
      +  "properties": {
      +    "evidence": {
      +      "description": "customer: priced at your own maxRuntimeSeconds | insufficient: nothing about this job predicts its runtime, so this is not a quote",
      +      "type": "string"
      +    },
      +    "includes": {
      +      "description": "What the estimate counts",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "nextStep": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "perHourUsd": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "What each hour of running costs on the machine Symbioza would book"
      +    },
      +    "summary": {
      +      "description": "One sentence for the user",
      +      "type": "string"
      +    },
      +    "unknown": {
      +      "description": "What it cannot count yet",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "evidence",
      +    "summary",
      +    "perHourUsd",
      +    "includes",
      +    "unknown",
      +    "nextStep"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / readiness
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "What stands between this estimate and a submittable one, plus advice about its inputs",
      +  "properties": {
      +    "missing": {
      +      "description": "budget_required | inputs_unverified | inputs_not_declared | access_required, each with a detail; the input notes are advice and never block a submit",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "detail": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "detail"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "description": "preliminary while budget_required or access_required is listed; otherwise ready",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "missing"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / runtime / description
      Previous value: -"basis, referenceSeconds, boundSeconds, boundBy, note: the runtime the price assumes and where the run would be stopped"New value: +"basis, referenceSeconds, boundSeconds, boundBy, note: the runtime the estimate assumes and where the run would be stopped"
    • changedOutput schema / properties / specDigest / description
      Previous value: -"Fingerprint of the exact spec and budget priced here; pass it to submitJob"New value: +"Fingerprint of the exact spec and budget priced here; pass it to submitJob. Absent when the spec has no budgetUsd: submitJob requires one"
  7. Changed6 schema fields changed
    • changedInput schema / properties / spec / properties / env / description
      Previous value: -"Environment variables for the container. They are stored with the job spec in clear on our control plane and are included in our routine backups, so do not put credentials or other secrets here — pass them in at run time or fetch them from your own store inside the command."New value: +"Non-sensitive configuration for the container (e.g. MODEL_NAME, EPOCHS). They are stored with the job spec in clear on our control plane and are included in our routine backups, so NEVER put credentials here: API keys, tokens, passwords and cloud keys belong in saved Secrets, attached with `secrets`."
    • addedInput schema / properties / spec / properties / secrets
      Added value: +{
      +  "description": "Saved secret sets this job needs, by name (e.g. [{\"name\":\"hf-training\"}]) or by the access it needs ([{\"type\":\"huggingface\",\"purpose\":\"Access a gated model\"}]). Every variable in each set is injected into the container at run time; values are never in the spec, the response or the chat. A missing set comes back with a Symbioza setup link for the user.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "fields": {
      +        "description": "For a custom requirement only: the environment variable NAMES the workload expects (e.g. [\"MODEL_API_TOKEN\"]). Names only, never values.",
      +        "items": {
      +          "pattern": "^[A-Za-z_][A-Za-z0-9_]{0,127}$",
      +          "type": "string"
      +        },
      +        "maxItems": 32,
      +        "type": "array"
      +      },
      +      "id": {
      +        "description": "The saved set's id (sec_…). Symbioza pins it at submit; you normally give the name.",
      +        "pattern": "^sec_[A-Za-z0-9_-]{22}$",
      +        "type": "string"
      +      },
      +      "name": {
      +        "description": "The saved secret set's name, e.g. \"hf-training\". Read the names with listSecrets.",
      +        "pattern": "^[a-z0-9][a-z0-9_-]{0,62}$",
      +        "type": "string"
      +      },
      +      "purpose": {
      +        "description": "A short reason shown to the user on the setup page, e.g. \"Access a gated model\". Never a credential.",
      +        "maxLength": 160,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "What access the workload needs: huggingface, object-storage, wandb or custom. With no name, Symbioza uses your one saved set of this type, or returns a setup link when there is none.",
      +        "enum": [
      +          "huggingface",
      +          "object-storage",
      +          "wandb",
      +          "custom"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "maxItems": 16,
      +  "type": "array"
      +}
    • addedOutput schema / properties / access
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "The saved secrets this spec attaches, by name and type only",
      +  "properties": {
      +    "complete": {
      +      "description": "true when every set the spec names is saved and nothing collides; submitJob refuses otherwise",
      +      "type": "boolean"
      +    },
      +    "conflicts": {
      +      "description": "A variable two attached sets (or a set and env) both define",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "nextAction": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "add_access | fix_spec | null"
      +    },
      +    "ready": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "fields": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "type",
      +          "fields"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "required": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "candidates": {
      +            "description": "ambiguous: the saved set names that could serve; ask the user which",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "purpose": {
      +            "type": "string"
      +          },
      +          "setupUrl": {
      +            "description": "missing: the Symbioza link where the user saves it; give it as returned",
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "missing | ambiguous | type_mismatch",
      +            "type": "string"
      +          },
      +          "type": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          }
      +        },
      +        "required": [
      +          "status",
      +          "type",
      +          "message"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "complete",
      +    "ready",
      +    "required",
      +    "conflicts",
      +    "nextAction"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / account / properties / shortfallUsd
      Added value: +{
      +  "description": "Whole dollars of credit this job still needs; 0 when it is covered",
      +  "type": "number"
      +}
    • changedOutput schema / properties / action / description
      Previous value: -"The one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, relax_spec_or_retry, retry_later, contact_support"New value: +"The one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, add_access, relax_spec_or_retry, retry_later, contact_support"
    • changedOutput schema / properties / code / description
      Previous value: -"Machine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, no_compute, unavailable, refused"New value: +"Machine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, access_required, secret_conflict, no_compute, unavailable, refused"
  8. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes far beyond them: it discloses that the call is free and books nothing, that maxRuntimeSeconds above 172800 is refused with invalid_spec, the no_compute and invalid_spec refusal shapes, the exact verified-image allowlist, and that specDigest gates submitJob. These are behavioral facts no annotation or schema conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical rule ('ALWAYS call the tool, never answer from memory') is front-loaded, which is good, but the body is a very long wall of text with visible redundancy — the runtime-boundary sentence ('only where the run would be stopped — a limit, never a prediction') and the budgetUsd hard-maximum point each appear more than once. Several sentences do not earn their place.

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 tool this complex — nested spec, secrets, account/access blocks, advisory warnings, specDigest chaining into submitJob — the description leaves nothing an agent needs to call it correctly. It even explains return values despite an output schema existing, and covers the refusal paths and funding/access recovery actions.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: budgetUsd is 'what you are willing to spend' and never exceeded, datasetGb must include data the box downloads itself, and gpu.minCudaVersion/gpuNameExact/minPowerLimitW are explained in terms of what market filtering they cause. It stops short of documenting every parameter, but the schema already covers the rest.

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 states a specific verb and resource (estimate a job's price) and adds the decisive scope fact — it is free and books nothing — which separates it from submitJob. The opening line even names the tool and its output ('estimateExecution for a price'), so an agent can distinguish it from getStatus/listJobs without opening a 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?

It gives explicit when/when-not rules: always call this rather than answering from memory, call once per spec+budget and only re-call when either changes, estimate first without budgetUsd and then ask for approval. It also routes to siblings by name, telling the agent to read the account before submitJob and to use listSecrets for set names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.