FINOS AI Governance MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Get Service Health

get_service_health

Queries each subsystem to report its real health status, so you can verify which services are currently operational and detect failures.

Instructions

Get real service health status by querying each subsystem.

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": "get_service_health"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`status`	Yes
`version`	Yes
`total_services`	Yes
`uptime_seconds`	Yes
`healthy_services`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the status is 'real' and obtained by querying each subsystem, which implies live aggregation rather than a cached read. It does not mention latency, timeouts, permissions, or whether querying subsystems has any side effects, leaving meaningful gaps for a no-annotation 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?

The description is a single front-loaded sentence with no filler. Every phrase earns its place by identifying the resource, its live nature, and the mechanism of querying subsystems.

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?

The tool is simple, takes no parameters, and has an output schema, so the description need not explain return values. It adequately conveys that health is determined by querying subsystems. Additional operational details such as timeout behavior or subsystem enumeration would improve completeness but are not strictly required.

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 no parameter meaning for the description to add. The baseline for a zero-parameter tool is 4, and the description does not create confusion about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: get service health status. It further clarifies that the status is 'real' and obtained 'by querying each subsystem,' which distinguishes it from sibling lookup tools like get_cache_stats or list_risks. It does not explicitly name a sibling alternative, but the resource is clearly distinct.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'service health status,' which suggests this tool is for checking live health. However, the description does not state when to use this instead of other diagnostics, nor does it mention prerequisites, exclusions, or alternatives. The guidance is adequate but minimal.

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

Deploy Server