Skip to main content
Glama

jdx_version

Returns the JDX server version the current instance was built as, optionally echoing a query label and selecting a stored workspace.

Instructions

The jdx version this server was built as.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional label echoed back in the envelope (empty is fine).
workspaceNoNamed workspace to answer from (default: the workspace the server was started with). Stored workspaces only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add the meaningful nuance that the value is the build-time jdx version rather than the currently installed binary, but it says nothing about the response shape, whether it is stable/cached, or why the workspace and query parameters would matter for a version lookup.

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 short sentence with no filler, front-loaded with the key noun (jdx version). The only cost is the slightly contorted 'built as' construction, which could be phrased more plainly.

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 low-complexity, zero-required-parameter tool with a fully described schema and no output schema, the description is minimally sufficient. It nevertheless leaves open whether the version is fixed for the server's lifetime and how the workspace parameter influences the answer.

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%, so both optional parameters are already documented, and the description adds no meaning beyond that. Notably it does not explain why a version tool accepts a workspace selector, which is the one place extra description would have helped.

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 the specific resource it reports (the jdx version) and qualifies it as the version 'this server was built as', which separates a build-time stamp from a runtime install. The verb is implicit rather than written ('returns/reports'), and the phrasing is slightly awkward, but an agent knows what it gets.

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?

No explicit when-to-use or when-not-to-use statement, and no alternatives named. Usage is implied by the tool's nature (checking version/provenance of the running server), which is adequate for a trivial informational tool but not stated.

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