Skip to main content
Glama

kernel-get_jvm_ergonomics

Retrieves JVM startup ergonomics—GC, heap limits, visible processors, container/cgroup limits, and large-page, CDS, and AOT-cache state—to diagnose runtime configuration.

Instructions

What the JVM running the kernel actually resolved at startup: selected GC, max/committed heap, visible processors, and the container limits it detected (cgroup CPU quota/period, memory cap, cpuset) plus large-page, CDS and AOT-cache state. Null fields mean the kernel could not determine that value. A kernel that does not implement this answers a snapshot with gcName 'unknown' and -1 byte counts.

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": "kernel-get_jvm_ergonomics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden and does so well: it states that values are a startup-time snapshot, that null means 'could not determine', and that an unimplemented kernel returns a snapshot with gcName 'unknown' and -1 byte counts. Those sentinel semantics are genuinely non-obvious and prevent misreading results. It omits any statement about access requirements or side-effect profile, keeping it short of a 5.

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?

The payload is front-loaded: the first clause states what the tool reports, then the field list, then the two caveats about nulls and unimplemented kernels. The field enumeration is dense but each item is informative rather than filler. Slight length pressure from the long parenthetical, but no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter getter with no output schema, the description must substitute for the return contract, and it does: it names the categories of values returned, the sentinel values for unknown fields, and the degraded response from non-implementing kernels. An agent has everything needed to call it and interpret the result correctly.

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, which is the baseline-4 case. The description is consistent with that, framing the call as a pure read of resolved state with nothing to configure, and adds no misleading hints about inputs.

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 opens with a specific verb-plus-resource framing ('What the JVM running the kernel actually resolved at startup') and enumerates the concrete values returned: selected GC, max/committed heap, visible processors, cgroup CPU quota/period, memory cap, cpuset, large-page, CDS and AOT-cache state. That is far more specific than a restatement of the name. It stops short of naming a sibling tool it differs from, so it lands at 4 rather than 5.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. Usage is only implied: an agent can infer this is the diagnostic call for 'what did the JVM/container environment actually look like', which is the rubric's definition of implied usage.

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