Skip to main content
Glama
Sign In
covera-mcp

covera-mcp

Official
by SuresoftTechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read a COVERA skill procedure

covera_get_guide
Read-only

Read topic-specific procedures for coverage builds, module measurement, and toolchain recovery so clients lacking COVERA skills can follow the same workflow.

Instructions

Return the procedure a COVERA skill follows, so a client without the skills can work the same way. Topics cover the coverage build flow, module measurement, and toolchain recovery, plus their reference documents. Read the matching topic before driving a flow.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "covera_get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhich procedure to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the content is procedural instructions plus reference documents intended to let a client imitate the skill, but it says nothing about the returned form (plain text vs structured) or size, which matters for a documentation-reading tool.

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?

Two sentences, purpose front-loaded, with the behavioral instruction second. 'plus their reference documents' is the only slightly vague clause, but nothing is redundant or padded.

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?

For a one-parameter, read-only documentation tool with an exhaustive enum and no output schema, the description supplies enough: what is returned, why, and what it covers. A note on the response format would close the remaining gap, but an agent can call it correctly as written.

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?

Schema coverage is 100% and the 24-value enum is fully documented as 'Which procedure to read.' The description only lightly extends this by grouping the enum into build flow, module measurement, and toolchain recovery topics — helpful framing but no per-value mapping beyond what the enum names already convey.

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?

Uses a specific verb ('Return') and resource ('the procedure a COVERA skill follows') and explains the intent behind it, so a client without native skills can replicate the flow. It does not name any sibling tool explicitly, but 'Read the matching topic before driving a flow' lets an agent place this as a prerequisite to the covera_coverage_* and covera_recovery_* actions.

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?

Gives clear situational guidance: read the matching topic before driving a flow, and it names the three domains (build, measurement, recovery) the topics span. It stops short of stating when *not* to call it or naming an alternative tool, but the pre-flight intent is unambiguous.

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