Skip to main content
Glama

Revnu

by com.revnu
OverviewDiscussionsAdmin

Get Revnu Status

agent_status
Read-onlyIdempotent

Check whether Revnu is working when the customer asks about progress or agent liveness. Returns status with the sandbox lifecycle state, last activity and finished-turn timestamps, whether a turn is running, and the number and next time of scheduled wakes. Read-only; does not start or interrupt work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesAgent liveness, activity and scheduled work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / status / properties / running / description
      Previous value: -"Whether recent invocation telemetry indicates an unfinished turn within the last 30 minutes. Poll agent_message_status for a particular request."New value: +"Whether a started turn has no exit yet and the agent wrote activity in the last 20 minutes. Poll agent_message_status for a particular request."
  2. Changed5 schema fields changed
    • changedOutput schema / properties / status / properties / lastActivityAt / description
      Previous value: -"Unix epoch milliseconds."New value: +"Most recent sandbox activity as Unix epoch milliseconds, or null when none is recorded."
    • changedOutput schema / properties / status / properties / lastTurnAt / description
      Previous value: -"Unix epoch milliseconds."New value: +"Most recent turn exit found in recent telemetry, as Unix epoch milliseconds, or null when none is found."
    • changedOutput schema / properties / status / properties / nextWakeAt / description
      Previous value: -"Unix epoch milliseconds."New value: +"Earliest pending wakeup as Unix epoch milliseconds, or null when none is scheduled."
    • addedOutput schema / properties / status / properties / pendingWakes / description
      Added value: +"Pending scheduled wakeups for this business, capped at 100; 100 can mean more exist."
    • addedOutput schema / properties / status / properties / running / description
      Added value: +"Whether recent invocation telemetry indicates an unfinished turn within the last 30 minutes. Poll agent_message_status for a particular request."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "status": {
+      "additionalProperties": true,
+      "description": "Agent liveness, activity and scheduled work.",
+      "properties": {
+        "lastActivityAt": {
+          "description": "Unix epoch milliseconds.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "lastTurnAt": {
+          "description": "Unix epoch milliseconds.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "nextWakeAt": {
+          "description": "Unix epoch milliseconds.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pendingWakes": {
+          "type": "number"
+        },
+        "running": {
+          "type": "boolean"
+        },
+        "sandbox": {
+          "description": "Sandbox lifecycle state, or none when no sandbox exists.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "sandbox",
+        "lastActivityAt",
+        "running",
+        "lastTurnAt",
+        "pendingWakes",
+        "nextWakeAt"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false; the description reinforces this and adds genuinely useful scope ('does not start or interrupt work'), which rules out a plausible misinterpretation. It stops short of noting cost, latency, or polling guidance.

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?

Two tight sentences with the purpose front-loaded and zero filler. Slight redundancy in enumerating return fields (status, timestamps, running turn, scheduled wakes) that the output schema already documents, but it stays compact.

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?

A no-parameter, read-only status probe with an output schema already in place. The description supplies the trigger condition, the read-only guarantee, and a preview of what status covers, so an agent has everything needed to call it correctly.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly implies a no-argument call.

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?

Specific verb (check) plus resource (Revnu / agent liveness) with a stated trigger situation. The scope is narrow and unambiguous, and it is easily separable from the surrounding sibling tools (leads, reviews, workflows), none of which overlap.

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?

Explicitly frames when to call it: 'when the customer asks about progress or agent liveness.' That is a clear usage context, though it names no alternative or exclusion, so an agent must still infer that this is the fallback liveness probe.

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

All Revnu 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