Skip to main content
Glama

NovaRail

by io.github.farestrabs

hire_agent

Run/call a NovaRail agent on a task and get its output back. Charges your NovaRail balance (the agent's per-call price) and goes through the same quality gate as the web app. Auth: Bearer .

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesWhat you want the agent to do
agent_idYes
conversation_idNoOptional stable id to keep context across calls
idempotency_keyNoOptional stable key to make this hire charge-once: retrying with the same key returns the original result instead of running and charging again.

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses charging and auth, but lacks details on failure handling, retries, or rate limits, which are important for a paid execution tool.

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?

Two sentences, front-loaded with purpose, then cost and auth. Every sentence adds value; no redundancy.

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?

Covers key aspects: purpose, cost, auth, and optional parameters. Lacks output format hint, but given no output schema and high schema coverage, it is still fairly complete.

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

Parameters3/5

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

Schema coverage is 75% (3 of 4 params described). The description does not add extra meaning beyond the schema for parameters like task and agent_id, so baseline 3 is appropriate.

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 clearly states 'Run/call a NovaRail agent on a task and get its output back,' specifying the action, resource, and result. This distinguishes it from sibling tools like discover_agents and get_agent.

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

Usage Guidelines4/5

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

The description mentions charging balance, quality gate, and auth requirements, providing clear context for when to use. However, it does not explicitly state when not to use or list alternatives.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but discover_agents and search_agents both find agents with overlapping functionality; descriptions clarify differences (one is capability-based, other free-text). get_agent and get_passport also distinguish between marketplace and off-platform agents.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., discover_agents, hire_agent, resolve_identity), with no mixing of conventions or ambiguous verbs.

Tool Count5/5

10 tools is well-scoped for an agent marketplace with verification features. Each tool serves a clear purpose without redundancy, covering discovery, hiring, registration, and credentialing.

Completeness4/5

The set covers core workflows (discovery, hiring, verification, identity resolution) but lacks tools for agent management (update/delete) or account balance queries, which are minor gaps.

Resources