Skip to main content
Glama
Sign In
covera-mcp

covera-mcp

Official
by SuresoftTechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Check the COVERA environment

covera_doctor
Read-only

Checks whether this MCP server can drive COVER by verifying Python, Local Agent path, cached Open API credentials, access key, and skill scripts; run it first when setup errors occur.

Instructions

Report whether this MCP server can drive COVER: the Python it runs on, whether CODESCROLL_TM_INSTALL_PATH points at a COVER EE Local Agent, whether cached Open API credentials exist, whether COVER_ACCESS_KEY is set, and which skill entry scripts are present. Needs no project. Run this first when other tools fail with setup errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the important operational facts that it requires no project context and is a diagnostic probe against local environment state. It does not say whether failures are surfaced as errors or as report content, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what it reports, followed by the no-prerequisite note and the escalation trigger; each clause carries information. The opening sentence is a long enumerated list, but every item maps to something the tool actually checks, so little is wasted.

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?

With no output schema, the description carries the report burden and it does so by enumerating the checked items. It stops short of describing the result shape (per-check pass/fail versus a single verdict), which would be the last piece an agent needs to interpret output.

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 takes zero parameters, so the baseline is 4; there is no parameter interpretation burden and nothing to compensate for. The description correctly implies a parameterless probe.

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 a precise resource: report whether this MCP server can drive COVER, then enumerates exactly what is inspected (Python version, CODESCROLL_TM_INSTALL_PATH, cached credentials, COVER_ACCESS_KEY, skill entry scripts). An agent can tell this apart from every sibling, which all act on coverage/recovery artifacts rather than environment health.

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?

"Run this first when other tools fail with setup errors" gives an explicit triggering condition, and "Needs no project" rules out a whole class of prerequisites. It does not name specific siblings whose errors should route here, so the agent must infer which failures are setup-related.

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

Deploy Server

Other Tools