Skip to main content
Glama

STATIC

STATIC supported languages

static_supported_languages
Read-onlyIdempotent

Languages, versions and development environments STATIC supports, from the STATIC 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": "static_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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds that results are drawn from two named source pages, hinting the tool may aggregate content, but says nothing about result shape, ordering, or how the optional filter behaves (exact match vs. substring).

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 short sentence with no filler, and the core subject matter leads. The only flaw is that it is a fragment lacking a leading verb, which slightly weakens the opening.

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?

This is a simple, zero-required-parameter read tool with no output schema, so expectations are modest. Still, with no output schema the description could have sketched what is returned (e.g. a per-language list with version and environment details), which it leaves unstated.

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 optional 'language' parameter already carries an example ('C/C++', 'Java'), so the schema does the work. The description adds no further semantics such as whether the filter is exact-match or case-sensitive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource clearly (languages, versions, development environments supported by STATIC) but is a noun phrase with no verb, so it never states that the tool *retrieves* or *lists* this information. It does not distinguish itself from siblings like static_overview or static_get_section, which could plausibly also cover supported-language content.

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 guidance and no mention of when not to use it or of an alternative tool. The only contextual hint is the sourcing note ('from the STATIC page and the Supported Languages page'), which is provenance rather than invocation guidance.

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