Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

compute_quote

Read-onlyIdempotent

Worst-case price of a job (its whole timeout) and whether compute_submit would take it from this...

Input Schema

NameRequiredDescriptionDefault
filesNo
publicNo
commandYes
timeout_sNo
result_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / command / description
      Removed value: -"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • removedInput schema / properties / files / description
      Removed value: -"relative path -> text content, put in the job folder (source only, no binaries)"
    • removedInput schema / properties / public / description
      Removed value: -"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • removedInput schema / properties / result_path / description
      Removed value: -"file the job writes its answer to, default result.json; it comes back as output"
    • removedInput schema / properties / timeout_s / description
      Removed value: -"seconds, default 120; the cap depends on your account's level (compute_backends)"
  2. Changed5 schema fields changed
    • addedInput schema / properties / command / description
      Added value: +"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • addedInput schema / properties / files / description
      Added value: +"relative path -> text content, put in the job folder (source only, no binaries)"
    • addedInput schema / properties / public / description
      Added value: +"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • addedInput schema / properties / result_path / description
      Added value: +"file the job writes its answer to, default result.json; it comes back as output"
    • addedInput schema / properties / timeout_s / description
      Added value: +"seconds, default 120; the cap depends on your account's level (compute_backends)"
  3. Changed5 schema fields changed
    • removedInput schema / properties / command / description
      Removed value: -"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • removedInput schema / properties / files / description
      Removed value: -"relative path -> text content, put in the job folder (source only, no binaries)"
    • removedInput schema / properties / public / description
      Removed value: -"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • removedInput schema / properties / result_path / description
      Removed value: -"file the job writes its answer to, default result.json; it comes back as output"
    • removedInput schema / properties / timeout_s / description
      Removed value: -"seconds, default 120; the cap depends on your account's level (compute_backends)"
  4. Changed5 schema fields changed
    • addedInput schema / properties / command / description
      Added value: +"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • addedInput schema / properties / files / description
      Added value: +"relative path -> text content, put in the job folder (source only, no binaries)"
    • addedInput schema / properties / public / description
      Added value: +"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • addedInput schema / properties / result_path / description
      Added value: +"file the job writes its answer to, default result.json; it comes back as output"
    • addedInput schema / properties / timeout_s / description
      Added value: +"seconds, default 120; the cap depends on your account's level (compute_backends)"
  5. Changed5 schema fields changed
    • removedInput schema / properties / command / description
      Removed value: -"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • removedInput schema / properties / files / description
      Removed value: -"relative path -> text content, put in the job folder (source only, no binaries)"
    • removedInput schema / properties / public / description
      Removed value: -"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • removedInput schema / properties / result_path / description
      Removed value: -"file the job writes its answer to, default result.json; it comes back as output"
    • removedInput schema / properties / timeout_s / description
      Removed value: -"seconds, default 120; the cap depends on your account's level (compute_backends)"
  6. Changed5 schema fields changed
    • addedInput schema / properties / command / description
      Added value: +"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • addedInput schema / properties / files / description
      Added value: +"relative path -> text content, put in the job folder (source only, no binaries)"
    • addedInput schema / properties / public / description
      Added value: +"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • addedInput schema / properties / result_path / description
      Added value: +"file the job writes its answer to, default result.json; it comes back as output"
    • addedInput schema / properties / timeout_s / description
      Added value: +"seconds, default 120; the cap depends on your account's level (compute_backends)"
  7. Changed5 schema fields changed
    • removedInput schema / properties / command / description
      Removed value: -"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • removedInput schema / properties / files / description
      Removed value: -"relative path -> text content, put in the job folder (source only, no binaries)"
    • removedInput schema / properties / public / description
      Removed value: -"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • removedInput schema / properties / result_path / description
      Removed value: -"file the job writes its answer to, default result.json; it comes back as output"
    • removedInput schema / properties / timeout_s / description
      Removed value: -"seconds, default 120; the cap depends on your account's level (compute_backends)"
  8. Changed5 schema fields changed
    • addedInput schema / properties / command / description
      Added value: +"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • addedInput schema / properties / files / description
      Added value: +"relative path -> text content, put in the job folder (source only, no binaries)"
    • addedInput schema / properties / public / description
      Added value: +"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • addedInput schema / properties / result_path / description
      Added value: +"file the job writes its answer to, default result.json; it comes back as output"
    • addedInput schema / properties / timeout_s / description
      Added value: +"seconds, default 120; the cap depends on your account's level (compute_backends)"
  9. Changed6 schema fields changed
    • removedInput schema / properties / command / items / properties
      Removed value: -null
    • removedInput schema / properties / command / properties
      Removed value: -null
    • removedInput schema / properties / files / properties
      Removed value: -null
    • removedInput schema / properties / public / properties
      Removed value: -null
    • removedInput schema / properties / result_path / properties
      Removed value: -null
    • removedInput schema / properties / timeout_s / properties
      Removed value: -null
  10. Changed11 schema fields changed
    • removedInput schema / properties / command / description
      Removed value: -"argv, e.g. [\"python3\", \"sim.py\"]; never a shell string"
    • addedInput schema / properties / command / items / properties
      Added value: +null
    • addedInput schema / properties / command / properties
      Added value: +null
    • removedInput schema / properties / files / description
      Removed value: -"relative path -> text content, put in the job folder (source only, no binaries)"
    • addedInput schema / properties / files / properties
      Added value: +null
    • removedInput schema / properties / public / description
      Removed value: -"true lets any machine on the network run it, including ones that joined self-serve; leave false for work you would not show a stranger"
    • addedInput schema / properties / public / properties
      Added value: +null
    • removedInput schema / properties / result_path / description
      Removed value: -"file the job writes its answer to, default result.json; it comes back as output"
    • addedInput schema / properties / result_path / properties
      Added value: +null
    • removedInput schema / properties / timeout_s / description
      Removed value: -"seconds, default 120; the cap depends on your account's level (compute_backends)"
    • addedInput schema / properties / timeout_s / properties
      Added value: +null
  11. Added

TDQS

C2.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the estimate is worst-case and spans the full job timeout, but the truncation means it does not fully disclose behavior beyond that.

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

Conciseness2/5

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

The single sentence is truncated with an ellipsis, so it is not structurally complete. It is short, but the brevity comes at the cost of clarity rather than efficient communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five undocumented parameters, no output schema, and a truncated description, an agent lacks enough information to call this correctly. It does not explain input formats, return value shape, or how the quote relates to compute_submit beyond a partial reference.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, including required command and optional files, public, timeout_s, and result_path. The description gives only a vague hint about 'its whole timeout' and does not explain the meaning or format of command, files, public, or result_path.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description indicates the tool computes a worst-case price for a job and checks whether compute_submit would accept it, which is more specific than the name alone. However, the sentence is truncated and does not cleanly state the verb/resource, leaving the purpose only partially clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It references compute_submit but does not explain when to use compute_quote versus compute_submit, print_plate_quote, ship_quote, or other pricing-related siblings. There are no explicit preconditions or exclusions.

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

All ce-net 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