Skip to main content
Glama
qiao-925
by qiao-925

ocr_health_check

Check the operational status of the OCR MCP Service to verify its readiness for processing image text extraction requests.

Instructions

Return lightweight health status for the stdio runtime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool registration and entry point for 'ocr_health_check'. It calls the health_service.build_response() method.
    @mcp.tool()
    def ocr_health_check() -> dict[str, Any]:
        """Return lightweight health status for the stdio runtime."""
        return health_service.build_response()
  • The implementation of the logic for the health check. It constructs a dictionary response containing health and uptime information.
    def build_response(self) -> dict[str, Any]:
        """Return the standardized health-check envelope."""
        health = ServiceHealth(
            status="healthy",
            uptime_ms=int((time.monotonic() - self._service_start_monotonic) * 1000),
            transport="stdio",
            runtime_version=__version__,
        )
        response = ToolResponse(
            status="ok",
            data=health.to_dict(),
            error=None,
            meta=ResponseMeta(
                timestamp=datetime.now(timezone.utc).isoformat(),
                runtime_version=__version__,
            ),
        )
        return response.to_dict()
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates the tool 'returns' health status, implying a read operation, but fails to explicitly state whether it is safe, idempotent, or has any side effects. The mention of 'lightweight' hints at performance characteristics but lacks detail.

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 consists of a single, efficient sentence of seven words that immediately communicates the tool's function. There is no redundant or extraneous information; every word earns its place.

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 (zero parameters) and the existence of an output schema (per context signals), the description is appropriately minimal. It adequately covers what the tool does without needing to elaborate on return values, though it could explicitly mention this is a non-destructive diagnostic operation.

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 with 100% schema description coverage. By the baseline rule for zero-parameter tools, this earns a 4. No additional parameter context is needed or provided in the description.

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 clearly states the tool returns a 'lightweight health status' for the 'stdio runtime', providing specific verb and resource information. It effectively distinguishes from sibling 'ocr_recognize' by indicating this is a health diagnostic rather than OCR functionality.

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?

The description provides no guidance on when to use this tool versus alternatives, or under what circumstances it should be invoked (e.g., before operations, for monitoring, etc.). No prerequisites or exclusions are mentioned.

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/qiao-925/ocr-mcp-service'

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