Skip to main content
Glama

tosea_health

Verify connectivity to ToseaAI's MCP server for document-to-presentation workflows including PDF parsing, outline generation, and slide rendering.

Instructions

Check MCP connectivity to ToseaAI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler implementation for the tosea_health tool. It calls the health() method on the ToseaClient.
    server.tool("tosea_health", "Check MCP connectivity to ToseaAI.", {}, async () => {
      try {
        return asToolResult(await client.health());
      } catch (error) {
        throw wrapToolError(error);
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks connectivity, implying a read-only, non-destructive operation, but doesn't specify what 'connectivity' entails (e.g., network status, API availability), expected response format, or any error handling. For a tool with zero annotation coverage, this is inadequate.

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: 'Check MCP connectivity to ToseaAI.' It is front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple tool, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior, output, or integration with siblings. For a connectivity check tool, more context on what 'connectivity' means and how results are interpreted would improve completeness.

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 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately focuses on the tool's purpose without redundant parameter information, earning a high score as it avoids unnecessary complexity.

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's purpose: 'Check MCP connectivity to ToseaAI.' It specifies the verb ('Check') and resource ('MCP connectivity to ToseaAI'), making it easy to understand. However, it doesn't explicitly differentiate from siblings like 'tosea_get_quota_status' or 'tosea_get_presentation_full_data', which might also involve connectivity checks, so it falls short of a perfect score.

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. It doesn't mention prerequisites, timing (e.g., before other operations), or exclusions. Given the sibling tools include various ToseaAI-related functions, the lack of usage context is a significant gap, though it's not misleading.

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/ToseaAI/mcp-ToseaAI'

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