Hermes Micro-Agent

by com.theworkpc.hermesmicroservice

Overview Discussions Admin

Get job status

get_job_status

Read-onlyIdempotent

Read the state, result, and error of one job by its job key.

Free to call, no authentication. States: pending_payment, paid, done, failed, refunded, cancelled.

Behavior: read-only, never raises. Returns found=false when no job has that key.

Parameters: an unknown key returns found=false, not an error.

When to use: after execute_task, or to recover a lost result. Use list_jobs to find keys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_key": "<job_key>"
    },
    "name": "get_job_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_key`	Yes	Job key returned by execute_task, or any job identifier you want to look up. Required.

Output Schema

Name	Required	Description
`task`	No
`cents`	No
`error`	No
`found`	Yes	false when no job exists with that key
`state`	No
`result`	No
`sender`	No
`job_key`	No
`tx_hash`	No
`created_at`	No
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, but the description goes further: it discloses that the call is free/unauthenticated, never raises, returns found=false for absent keys, and enumerates the full state set (pending_payment through cancelled). The 'unknown key returns found=false, not an error' detail is exactly the kind of error-contract behavior annotations cannot express.

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

Conciseness4/5

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

Front-loaded with the core purpose, then cleanly partitioned into Behavior, Parameters, and When to use. The only waste is the redundancy between 'Returns found=false when no job has that key' and the Parameters line restating the same behavior.

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?

An output schema exists, so return shape needs no explanation, and the description supplies everything else an agent needs: auth cost, state vocabulary, no-raise error contract, and sibling routing. Nothing material is missing for a single-parameter read tool.

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 coverage is 100% and the single parameter is already documented, so baseline would be 3. The description adds meaning beyond it by specifying the failure semantics of the parameter ('an unknown key returns found=false, not an error'), though it slightly repeats that point elsewhere.

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?

States a specific verb and resource with scope: 'Read the state, result, and error of one job by its job key.' The singular 'one job' plus the job-key lookup distinguishes it from the sibling list_jobs without needing to open either 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?

Gives an explicit 'When to use' section tied to a concrete sibling ('after execute_task, or to recover a lost result') and routes key discovery to list_jobs. The agent knows both why to call this and what to call instead when it lacks a key.

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

All Hermes Micro-Agent tools Inspect

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

Need Help?