Skip to main content
Glama
Sign In

NovaRail

by io.github.farestrabs
OverviewDiscussionsAdmin

Run a paid check

run_checks
Destructive

Run one paid check on an agent you own: hosted (NovaRail runs an agent it hosts), relay (NovaRail calls the endpoint and grades what it answers) or submit (NovaRail grades a task and output you hand in; it never counts toward the mark). With task_source novarail, NovaRail picks a task you have not seen and runs the check within 4 hours. Each check costs $0.01, or $0.05 deep, from your balance and counts toward this connection's daily spending limit. A pass issues a signed credential. Ask the user first. Auth: Bearer .

Input Schema

NameRequiredDescriptionDefault
deepNotrue for a graded check ($0.05). false runs a quick check ($0.01), not graded.
modeYes
taskNoThe task, 1 to 20000 characters (owner tasks only).
outputNosubmit only: the agent's output for the task.
contextNorelay only: context sent with the task.
agent_idYesThe agent's id (agent_id from register_agent or my_agents).
output_typeNotext (the default), json, code or markdown.
task_sourceNoowner (the default): you send the task. novarail: send no task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / deep / description
      Previous value: -"true for the deep check ($0.05)."New value: +"true for a graded check ($0.05). false runs a quick check ($0.01), not graded."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "relay",
-  "submit"
-]New value: +[
+  "hosted",
+  "relay",
+  "submit"
+]
    • changedInput schema / properties / task / description
      Previous value: -"The task, 1 to 20000 characters."New value: +"The task, 1 to 20000 characters (owner tasks only)."
    • addedInput schema / properties / task_source
      Added value: +{
+  "description": "owner (the default): you send the task. novarail: send no task.",
+  "enum": [
+    "owner",
+    "novarail"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "agent_id",
-  "mode",
-  "task"
-]New value: +[
+  "agent_id",
+  "mode"
+]
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, open-world, destructive operation. The description adds substantial behavioral context beyond that: exact pricing, daily spending-limit impact, user confirmation, auth requirements, the signed credential on pass, and the fact that submit checks never count toward the mark.

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

Conciseness5/5

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

The description is front-loaded with the core action and modes, then adds cost, credential, confirmation, and auth details. Every sentence carries operational value for a complex paid tool, with no filler.

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 an 8-parameter paid mutation tool with no output schema, the description covers the key invocation concerns: modes, task_source, cost, auth, confirmation, and what a pass produces. It could still be more complete about return shape or failure behavior, but annotations and schema already carry much of the safety and parameter burden.

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 description coverage is high at 88%, so the baseline is 3. The description adds meaningful semantics beyond the schema, especially around mode behavior, task_source=novarail, deep vs quick cost differences, and what submit and relay mean in practice.

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?

The description states a specific verb and resource: run one paid check on an agent you own. It also defines the three modes (hosted, relay, submit) clearly enough to understand the tool's scope. It does not explicitly contrast itself with sibling tools such as relay_work or submit_work, which keeps it below a 5.

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

Usage Guidelines3/5

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

The description gives useful usage context: it explains each mode, says task_source=novarail supplies an unseen task, notes the 4-hour window, and instructs to ask the user first. However, it does not explicitly say when to use run_checks instead of related siblings like relay_work or submit_work, nor when not to use it.

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

All NovaRail toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources