Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

compute_check

Read-onlyIdempotent

The door's and the machine's rules over a job (argv and every file) without running it; no model...

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description reinforces that nothing is executed, but adds little about what rules are checked, what a failure looks like, or what is returned.

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?

It is short, but the single sentence is cryptic and appears truncated ("no model..."), so it is not front-loaded with a clear purpose. Brevity here reflects under-specification rather than efficient structure.

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?

For a tool with five parameters, zero schema description coverage, a nested files object, and no output schema, the description is far too thin. It does not explain the validation outcome or how the check relates to compute_submit.

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%, so the description must compensate, but it only vaguely gestures at argv and files. It says nothing about public, timeout_s, or result_path, leaving most parameters unexplained.

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

Purpose2/5

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

The description says it checks a job "without running it," which hints at validation, but the phrasing "The door's and the machine's rules over a job" is opaque and never states a clear verb+resource. It does not distinguish compute_check from siblings such as compute_submit or compute_quote.

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?

There is no explicit guidance on when to use this versus compute_submit, compute_quote, or other compute siblings. "Without running it" weakly implies a preflight check, but no alternatives or exclusions are named.

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