Generect

Server and credential health (free)

health

Read-onlyIdempotent

Liveness check. Free: this call never spends credits. Confirms the MCP server is up, reports its version and (unless disabled) verifies the credential against a free account endpoint. It never touches a paid data endpoint, so it is safe for monitors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "health"
  }
}

Input Schema

Name	Required	Description	Default
`timeout_ms`	No	Request timeout in milliseconds.
`check_credential`	No	Also verify the API token against the free /accounts/me endpoint. Default true.

Output Schema

Name	Required	Description	Default
`ms`	No
`ok`	No
`cost`	No
`server`	No
`account`	No
`version`	No
`api_base`	No
`test_mode`	No
`balance_usd`	No
`has_credential`	No
`credential_error`	No
`credential_valid`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / deprecated_params_ignored / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "account": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "api_base": {
+      "type": "string"
+    },
+    "balance_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "credential_error": {},
+    "credential_valid": {
+      "type": "boolean"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "has_credential": {
+      "type": "boolean"
+    },
+    "ms": {
+      "type": "number"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "server": {
+      "type": "string"
+    },
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedSep 10, 2026

addedInput schema / properties / check_credential

Added value: +{
+  "description": "Also verify the API token against the free /accounts/me endpoint. Default true.",
+  "type": "boolean"
+}

removedInput schema / properties / deep

Removed value: -{
-  "description": "Run a live API probe (lead-by-link). Consumes a credit. Default false.",
-  "type": "boolean"
-}

changedInput schema / properties / timeout_ms / description

Previous value: -"Request timeout in milliseconds"New value: +"Request timeout in milliseconds."

removedInput schema / properties / url

Removed value: -{
-  "description": "LinkedIn profile URL for the deep probe (defaults to a public profile).",
-  "type": "string"
-}

Changed2 schema fields changedJul 17, 2026

addedInput schema / properties / deep

Added value: +{
+  "description": "Run a live API probe (lead-by-link). Consumes a credit. Default false.",
+  "type": "boolean"
+}

changedInput schema / properties / url / description

Previous value: -"LinkedIn profile URL to validate (defaults to a public profile)"New value: +"LinkedIn profile URL for the deep probe (defaults to a public profile)."

First observedFeb 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, and the description adds real behavioral context: it costs no credits, never touches a paid data endpoint, and its credential check hits a free /accounts/me endpoint. The only missing piece is any note on latency or failure behavior, which keeps it at 4 rather than 5.

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?

Four short sentences, front-loaded with 'Liveness check.' and the free-cost guarantee immediately after. Every sentence carries distinct information (cost, what's checked, endpoint scope, monitor safety) with no filler.

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 values need no explanation, and the description covers cost, scope, optional credential verification, and safety. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so both parameters are already documented in the schema. The description's 'unless disabled' clause loosely maps to check_credential and the free endpoint is named, but it adds little beyond the schema's own wording — the baseline 3 applies.

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: 'Liveness check' that 'Confirms the MCP server is up, reports its version' and optionally verifies the credential. This is unmistakably distinct from the data-oriented siblings (search_leads, get_balance, enrich_company), so an agent can select it without opening the schema.

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?

Gives clear usage context — 'safe for monitors' and 'never spends credits' — which tells the agent this is the cheap pre-flight/uptime check. It does not explicitly name an alternative or state when-not-to-use, so it falls short of the 5-level routing guidance.

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

All Generect 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.