Skip to main content
Glama

SURESOFT CT

CT supported languages

ct_supported_languages
Read-onlyIdempotent

Languages, versions and development environments CT supports, from the CT 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": "ct_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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safe, deterministic read profile is fully covered. The description adds only the provenance detail (CT page and Supported Languages page), and says nothing about whether an unmatched language returns empty, an error, or the full list.

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?

One compact sentence with the resource front-loaded and no wasted clauses. The trailing provenance phrase ('from the CT page and the Supported Languages page') is slightly internal-sounding but does convey where the data lives.

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 reference tool with no output schema, the description covers the subject matter but not the shape of the result (e.g., whether versions are grouped per language). It is adequate to invoke the tool but leaves the agent guessing about output structure and no-match behavior.

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 description coverage is 100% and the single 'language' parameter already carries an example ('C/C++', 'Java') and optionality. The description adds no further meaning — no guidance on exact-match requirements, casing, or whether unknown values are tolerated — so the baseline of 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 identifies a specific resource — the languages, versions and development environments CT supports — which is concrete enough for an agent to know what it retrieves. It does not, however, distinguish itself from siblings such as ct_overview or ct_get_section, which could plausibly also surface this content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: by describing the content as the set of supported languages/versions, it signals 'call this when you need compatibility info.' There is no explicit when-to-use statement, no mention of alternatives like ct_search_faq for related questions, and no note that the single param is the only narrowing mechanism.

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