ravn_healthLiveness check across every venue RAVN routes through — call before a swap if you want to know whether a route is degraded ahead of time.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "additionalProperties": false,
- "properties": {
- "status": {
- "enum": [
- "ok",
- "degraded"
- ],
- "type": "string"
- },
- "venues": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "healthy": {
- "type": "boolean"
- },
- "id": {
- "type": "string"
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "name",
- "healthy"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "status",
- "venues"
- ],
- "type": "object"
- },
- "meta": {
- "additionalProperties": false,
- "properties": {
- "requestId": {
- "type": "string"
- },
- "version": {
- "type": "string"
- }
- },
- "required": [
- "requestId",
- "version"
- ],
- "type": "object"
- }
- },
- "required": [
- "data",
- "meta"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "type": "string"
- },
- "details": {},
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ],
- "type": "object"
- },
- "meta": {
- "additionalProperties": false,
- "properties": {
- "requestId": {
- "type": "string"
- },
- "version": {
- "type": "string"
- }
- },
- "required": [
- "requestId",
- "version"
- ],
- "type": "object"
- }
- },
- "required": [
- "error",
- "meta"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "status": {
+ "enum": [
+ "ok",
+ "degraded"
+ ],
+ "type": "string"
+ },
+ "venues": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "healthy": {
+ "type": "boolean"
+ },
+ "id": {
+ "type": "string"
+ },
+ "logoUrl": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "healthy"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "status",
+ "venues"
+ ],
+ "type": "object"
+ },
+ "meta": {
+ "additionalProperties": false,
+ "properties": {
+ "requestId": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "requestId",
+ "version"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "data",
+ "meta"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "details": {},
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ },
+ "meta": {
+ "additionalProperties": false,
+ "properties": {
+ "requestId": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "requestId",
+ "version"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error",
+ "meta"
+ ],
+ "type": "object"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "status": {
+ "enum": [
+ "ok",
+ "degraded"
+ ],
+ "type": "string"
+ },
+ "venues": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "healthy": {
+ "type": "boolean"
+ },
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "healthy"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "status",
+ "venues"
+ ],
+ "type": "object"
+ },
+ "meta": {
+ "additionalProperties": false,
+ "properties": {
+ "requestId": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "requestId",
+ "version"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "data",
+ "meta"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "details": {},
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ },
+ "meta": {
+ "additionalProperties": false,
+ "properties": {
+ "requestId": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "requestId",
+ "version"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error",
+ "meta"
+ ],
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses that the check spans all venues, is a liveness probe (not a performance metric), and is intended as a pre-swap gate — behavior the annotations alone don't convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads what the tool is before adding the usage hint. No redundant restatement of the title or annotation flags; every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, an output schema present, and annotations covering read-only/open-world semantics, the description supplies exactly the remaining context an agent needs: what it checks and when to call it. Nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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; the baseline for a 0-param tool applies. The description correctly implies the scope is global across venues, matching the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('liveness check') and a precise scope ('across every venue RAVN routes through'), which makes it clear this is a health probe rather than a quote or execute. It does not explicitly differentiate itself from the similarly-named sibling ravn_status, so the agent must infer the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'call before a swap if you want to know whether a route is degraded ahead of time' gives a clear trigger condition and intent. It stops short of naming alternatives (e.g. ravn_status) or saying when not to bother, so the routing guidance is contextual rather than exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.