flowforge-mcp

flowforge_health

Read-onlyIdempotent

Verifies the FlowForge host is reachable, reports the targeted base URL and bundled spec version, and helps diagnose connection errors before using other tools.

Instructions

Check the FlowForge host is up (unauthenticated GET /health) and report which base URL this server targets and which spec version it bundles.

Use first when other tools return connection errors.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered by structured data. The description adds genuinely new behavioral context: the call is unauthenticated (no API key needed) and it returns diagnostic metadata rather than domain data. It doesn't mention latency, caching, or whether the health result is cached, but that is minor here.

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?

Two short sentences: the first defines what is checked and what is reported, the second front-loads the operational trigger. No filler, no repetition of the tool name, and the most actionable guidance sits at the end where it is easy to scan.

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?

For a zero-parameter diagnostic with an output schema, the description covers purpose, endpoint behavior, reported values, and a usage trigger. There is no ambiguity an agent would need resolved before calling it.

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 schema declares an empty HealthInput with description "No inputs", and the description is consistent with a zero-argument call, so nothing is missing. The required "params" wrapper is an artifact of the schema shape rather than a meaningful parameter, and the description correctly avoids inventing argument semantics for it.

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 ("check the FlowForge host is up") and names the exact endpoint semantics (unauthenticated GET /health). It also distinguishes itself from data-oriented siblings by declaring it reports the targeted base URL and bundled spec version, so an agent can tell it apart from flowforge_api_reference or any CRUD tool.

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 an explicit triggering condition: "Use first when other tools return connection errors." That is a clear when-to-use rule tied to sibling failure modes. It stops short of stating when-not-to-use (e.g., don't call during normal happy-path operation), which keeps it from a 5.

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

Deploy Server