Skip to main content
Glama

COVER

COVER supported languages

cover_supported_languages
Read-onlyIdempotent

Languages, versions and development environments COVER supports, from the COVER page and the Supported Languages page.

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": "cover_supported_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional: limit to one language, e.g. "C/C++", "Java".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is fully covered. The description adds a modest amount of context by attributing the data to the COVER page and Supported Languages page, implying a static reference dataset, but says nothing about return shape or whether the list is exhaustive.

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?

A single efficient sentence with the resource front-loaded. The trailing source attribution is marginally redundant but not wasteful, and no padding or restatement of the title occurs.

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?

For a one-optional-parameter read-only lookup with no output schema, the definition is adequate but thin: it does not describe what a result entry contains (language plus versions plus environments, presumably) or whether an unfiltered call returns everything. An agent can call it, but cannot predict the response shape.

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 single optional language parameter is already documented with an example value in the schema. The description never mentions the filter, so it adds no meaning beyond the schema; baseline 3 applies.

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 names a specific resource (COVER-supported languages, versions, development environments) and its sources, so an agent knows this is a lookup/reference tool. It does not explicitly distinguish itself from siblings like cover_overview or cover_resources, which keeps it short of a 5.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The agent must infer that this is the tool for support-matrix questions and cannot tell from the text whether cover_overview or cover_search_faq would be a better first call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources