Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_health_cache

Check BOS cache system health to identify issues and ensure reliable performance.

Instructions

Check BOS cache systems

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'boscli_health_cache' tool. It makes a GET request to '/boscli/health/cache' via the BosApiClient to check BOS cache systems.
    handler: async (_, client) => client.get('/boscli/health/cache'),
  • The schema for the 'boscli_health_cache' tool is an empty object, meaning it takes no input parameters.
    schema: {},
  • The tool is registered as part of the 'healthTools' array exported from src/tools/health.ts, which is a list of McpTool objects.
    export const healthTools: McpTool[] = [
      {
        name: 'boscli_health_check',
        description: 'Full BOS system health check - modules, database, cache, routes',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health'),
      },
      {
        name: 'boscli_health_modules',
        description: 'Check health of all BOS modules',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/modules'),
      },
      {
        name: 'boscli_health_database',
        description: 'Check BOS database connectivity',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/database'),
      },
      {
        name: 'boscli_health_cache',
        description: 'Check BOS cache systems',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/cache'),
      },
      {
        name: 'boscli_health_schema',
        description: 'Check BOS database schema integrity',
        schema: {},
        handler: async (_, client) => client.get('/boscli/health/schema'),
      },
    ];
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. 'Check' implies a read-only operation, but there is no detail on what the check entails, side effects, or return behavior. Insufficient for a non-trivial health check.

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?

The description is a single sentence, which is concise but overly minimal. It could be slightly expanded while remaining efficient.

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?

Given the absence of an output schema, the description should explain what the tool returns (e.g., health status, metrics). It fails to do so, making it incomplete for an effective agent invocation.

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?

There are no parameters, so the baseline is 4. The description adds no extra semantics because none are needed.

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 'Check BOS cache systems' clearly indicates the tool's purpose (verb+resource), but it does not distinguish it from sibling health-check tools like boscli_health_database or boscli_health_modules, which are likely for different subsystems.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context for usage, exclusions, or preconditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bizino/bos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server