FINOS AI Governance MCP Server

Official

by finos

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Get Cache Stats

get_cache_stats

Retrieve cache statistics to monitor performance and diagnose caching behavior in the AI governance MCP server.

Instructions

Get cache statistics.

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_cache_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`hit_rate`	Yes
`cache_hits`	Yes
`cache_misses`	Yes
`total_requests`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses essentially nothing: not whether this is a cheap read, whether it hits a live service, whether results are point-in-time snapshots, or what permissions are needed. Only the verb "get" weakly implies a read-only operation.

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

Conciseness3/5

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

It is a single short sentence with no wasted words and is trivially front-loaded, but the brevity comes from under-specification rather than efficient communication. Nothing in it earns its place beyond the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 not be described, and the empty input schema needs no elaboration. However, for a tool with zero annotations and no argument surface to convey meaning, the description should carry the behavioral context and instead says nothing beyond the name.

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 semantics to explain; the baseline for a no-argument tool applies. Nothing in the description contradicts or obscures the empty input schema.

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

Purpose2/5

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

"Get cache statistics." restates the tool name and title almost verbatim, adding no specificity about which cache, what statistics, or what scope. It does not differentiate this tool from siblings like get_service_health, which an agent could plausibly confuse it with.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. The agent must infer entirely on its own that this tool is for inspecting cache state rather than, say, clearing or warming a cache.

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

Deploy Server