Skip to main content
Glama

Inspect Jeb Client

inspect_jeb_client
Idempotent

Inspect a running JEB client serving MCP to read its engine version, GUI or headless mode, and startup time without opening a target; the client must already be reachable at REA_JEB_MCP_URL.

Instructions

Inspect the running JEB client serving MCP: engine version, GUI or headless mode, and startup time. Does not open a target. Requires a caller-started JEB client reachable at REA_JEB_MCP_URL (default http://127.0.0.1:8425/mcp); REA never installs or launches JEB.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_jeb_client"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the external dependency (a caller-managed JEB client at a configurable URL) and the negative behavior 'does not open a target', which is exactly the kind of context annotations cannot convey. There is mild tension with readOnlyHint=false for a tool that reads version/mode/startup data, but the openWorldHint=true network dependency plausibly explains it rather than contradicting the text.

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?

Two sentences, front-loaded with what is returned and followed by the precondition. Nothing is redundant: the returned fields, the non-action, the endpoint requirement, and the ownership boundary each carry distinct information.

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?

With no output schema, the description compensates by enumerating the returned fields, and with no parameters there is nothing else to document. The only remaining unknown — behavior on an unreachable client — is strongly implied by the 'requires a reachable client' clause.

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 and the schema is an empty object with additionalProperties=false, so there is no parameter semantics to add; the description correctly implies a no-argument call. Baseline 4 for a zero-param tool is appropriate.

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

Purpose5/5

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

The description names a specific verb and resource ('Inspect the running JEB client serving MCP') and enumerates exactly what it reports: engine version, GUI vs. headless mode, and startup time. The clause 'Does not open a target' plus the JEB-specific naming cleanly separates it from siblings like open_jeb_project, decompile_jeb_item, and the other inspect_*_client probes for ADB/APKTool.

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

Usage Guidelines4/5

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

It gives a clear precondition — a caller-started JEB client reachable at REA_JEB_MCP_URL with the default endpoint — and states REA never installs or launches JEB, which tells the agent this is a connectivity/version probe rather than a work-doing tool. It stops short of explicitly saying 'call this first to verify JEB is up before invoking decompile_jeb_item', so the sequencing against siblings is left implied.

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

Deploy Server

Other Tools