Skip to main content
Glama

Get Server Version

get_version
Read-onlyIdempotent

Retrieve the JavaBytes server and Java runtime version numbers to verify compatibility and troubleshoot environment issues.

Instructions

Return the JavaBytes server and Java runtime versions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/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 safety profile is fully covered by structured data. The description's only added behavioral value is identifying that the response covers both the JavaBytes server and the Java runtime. It says nothing about cost, secrets exposure, or result shape.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the resource is named immediately and nothing is wasted. It could arguably be trimmed to 'server and Java versions', but every word carries information.

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 zero-parameter informational tool with rich annotations, the description is nearly sufficient. Because there is no output schema, the description has to hint at return contents, which it does by naming the two version values; it just lacks any return format detail such as version string style or response key names.

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 there is nothing for the description to disambiguate and the baseline is 4. The description correctly presents this as a parameterless call.

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?

States a specific verb ('Return') and resource ('JavaBytes server and Java runtime versions'), which is far more precise than a tautological restatement of the title. It does not explicitly distinguish itself from nearby informational siblings like get_system_info or environment_variables, but the scope is narrow and legible.

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: an agent can infer it should call this when it needs environment/version context, likely for diagnostics or compatibility checks. There is no explicit when-to-use statement, no exclusion, and no pointer to get_system_info for the broader environment picture.

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