Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

by cmendezs
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

healthcheck_flow

Check the operational status of the Approved Platform's Flow Service before submitting invoices. Ensures the service is reachable and returns status as ok, degraded, or unavailable.

Instructions

Check the availability of the Approved Platform's Flow Service. Returns the operational status of the service (ok/degraded/unavailable). Use before an invoice submission session to ensure the AP is reachable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/flow_tools.py:354-361 (handler)
    MCP tool handler that checks Flow Service availability by delegating to FlowClient.healthcheck()
    async def healthcheck_flow() -> dict:
    """
    Check the availability of the Approved Platform's Flow Service.
    Returns the operational status of the service (ok/degraded/unavailable).
    Use before an invoice submission session to ensure the AP is reachable.
    """
    client = get_flow_client()
    return await client.healthcheck()
  • tools/flow_tools.py:353-361 (registration)
    Decorator registration on FastMCP instance inside register_flow_tools()
    @mcp.tool()
async def healthcheck_flow() -> dict:
    """
    Check the availability of the Approved Platform's Flow Service.
    Returns the operational status of the service (ok/degraded/unavailable).
    Use before an invoice submission session to ensure the AP is reachable.
    """
    client = get_flow_client()
    return await client.healthcheck()
  • tools/flow_tools.py:354-361 (schema)
    No input parameters (empty schema); returns dict with status field
    async def healthcheck_flow() -> dict:
    """
    Check the availability of the Approved Platform's Flow Service.
    Returns the operational status of the service (ok/degraded/unavailable).
    Use before an invoice submission session to ensure the AP is reachable.
    """
    client = get_flow_client()
    return await client.healthcheck()
  • clients/flow_client.py:167-173 (helper)
    FlowClient.healthcheck() — actual HTTP call to GET /v1/healthcheck
    async def healthcheck(self) -> dict[str, Any]:
    """GET /v1/healthcheck — Check Flow Service availability."""
    response = await self._request("GET", "/v1/healthcheck")
    try:
        return response.json()
    except Exception:
        return {"status": "ok", "http_status": response.status_code}
  • server.py:63-64 (registration)
    Top-level registration call in server.py entry point
    register_flow_tools(mcp)
register_directory_tools(mcp)

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Discloses return statuses (ok/degraded/unavailable). No annotations provided, so description carries full burden; no mention of authentication or side effects, but healthcheck is inherently safe.

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?

Three concise sentences: purpose, output, usage guidance. No redundancy or filler.

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?

Complete coverage for a zero-parameter tool with output schema. Clearly defines purpose, return values, and use case.

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?

No parameters in schema (0 params, baseline 4). Description adds value by explaining the check target and return values.

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?

Clearly states 'Check the availability of the Approved Platform's Flow Service', using specific verb and resource. Distinguishes from sibling tools like get_flow and submit_flow.

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?

Explicitly suggests using before an invoice submission session to ensure AP is reachable. Lacks explicit when-not-to-use, but context is clear.

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/cmendezs/mcp-facture-electronique-fr'

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