Skip to main content
Glama
Sign In
forgespec-mcp

forgespec-mcp

by lleontor705
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

forgespec_health

Read-onlyIdempotent

Check server health diagnostics, verify database integrity, inspect active leases, and review version telemetry to identify and resolve system issues.

Instructions

Get server health diagnostics, database integrity status, system time, active leases, and version telemetry.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds value by listing the specific data categories returned (database integrity, system time, etc.), which enriches the agent's understanding of the tool's output beyond the annotations. It does not contradict annotations.

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, clear sentence listing all returned items without redundancy. It is front-loaded and contains no filler, making it highly efficient.

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?

Given the tool's simplicity (no params, no output schema), the description adequately conveys the purpose and return content. It lists the main categories of data, which is sufficient for a health check. It could mention the output format, but that is not critical for this low-complexity tool.

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 has zero parameters, so the schema is fully covered (100%). With no parameters to explain, the description need not add parameter details. The baseline of 4 for no-parameter tools is appropriate.

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?

The description clearly states the tool retrieves server health diagnostics, database integrity, system time, active leases, and version telemetry. The verb 'Get' plus the specific resource types make the purpose unambiguous and distinguish it from sibling tools like tb_status or tb_heartbeat, which address task/system liveness rather than full health diagnostics.

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?

The description implies its use for health checks but does not explicitly state when to use it relative to alternatives. It lacks guidance on when not to use it or how it differs from similar status tools. The usage context is implicit rather than explicit.

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

Deploy Server

Other Tools