Skip to main content
Glama
Correctover

Correctover MCP Server

Official

chat

Read-only

Send messages to an LLM with automatic output verification across 6 dimensions (structure, latency, cost, etc.) and auto-healing on failure.

Instructions

Send a chat message to an LLM with automatic output verification. Routes through the best available provider, validates the response across 6 dimensions (structure, schema, latency, cost, identity, integrity), and auto-heals on failure by retrying or failing over to another provider. Returns the response text plus a validation report showing which dimensions passed or failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel name or 'auto' for automatic provider selection. Examples: 'gpt-4o-mini', 'claude-3-haiku-20240307', 'deepseek-chat'. Default: 'auto'.
messagesYesConversation messages in OpenAI format: [{role: 'user', content: '...'}, ...]. Each message must have 'role' (system/user/assistant) and 'content' (string).
providerNoForce a specific provider: 'openai', 'anthropic', 'deepseek', 'moonshot', 'zhipu', 'qwen', 'siliconflow', 'groq', 'together'. If omitted, auto-selects by priority and health.
max_tokensNoMaximum tokens in response. Limits output length to control cost and latency.
temperatureNoSampling temperature (0.0-2.0). Lower values for more deterministic output. Default: provider-specific.
system_promptNoSystem prompt to prepend to the conversation. Useful for setting context, role, or output format requirements.
Behavior1/5

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

The description contradicts the annotation readOnlyHint=true by stating it sends a chat message, which is a write operation. Despite providing additional behavioral details like auto-healing, the contradiction reduces transparency score to 1 per rules.

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 three sentences long, front-loads the main action, and every sentence adds value without redundancy. It is 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?

The description covers key aspects: what it does, routing, validation, auto-heal, and return type. However, it lacks details on error handling and the exact structure of the validation report. Given no output schema, slightly more detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description does not add new meaning beyond the schema; it only summarizes the tool's behavior. No per-parameter elaboration.

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's purpose: sending a chat message with automatic output verification. It distinguishes itself from sibling tools (health, providers, stats, validation_history) which serve different functions.

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?

The description explains when to use the tool (for chat with verification) but lacks explicit guidance on when not to use it or alternatives. The context is clear, but no exclusions or comparisons are provided.

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/Correctover/mcp-server'

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