Skip to main content
Glama

Open Jeb Project

open_jeb_project

Opens or creates a JEB project from an artifact file or existing .jdb2 database on the engine host, returning input-file digests and top-level units for analysis.

Instructions

Open or create a JEB project from an artifact file or existing .jdb2 database on the engine host. Returns the project's input-file digests and top-level units. The engine analyzes the target itself; REA does not read the file or execute it. Fails when a project is already open.

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": {
      "path": "/tmp/Example.apk"
    },
    "name": "open_jeb_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesArtifact file or existing .jdb2 project database, resolved by the running JEB client

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds genuinely new behavior beyond that: the state precondition 'Fails when a project is already open,' that analysis happens engine-side, and that the file is not read or executed locally. The only gap is that it does not say what happens to an existing open project or whether the return digests can be used for change detection.

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?

Three sentences, each carrying distinct information: action and input, return shape, security/execution model, and the failure precondition. The core action is front-loaded with no filler.

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 one-parameter mutation tool with no output schema and rich annotations, the description covers the action, the return payload (input-file digests and top-level units), the execution boundary, and the primary failure mode. Nothing material is missing for an agent to call it correctly.

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 a single parameter is fully documented in the schema, so the baseline of 3 applies. The description restates that the path may be an artifact or a .jdb2 database 'on the engine host,' which adds a small amount of resolution context but no new syntax or format detail.

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 gives a precise verb pair ('open or create') and resource ('a JEB project'), plus the accepted inputs (artifact file or existing .jdb2 database on the engine host). It separates itself from file-touching tools by noting 'REA does not read the file or execute it,' though it never names a sibling such as open_binary for direct contrast.

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 context is implied: reach for this when you need a JEB project built from a host-side artifact or existing .jdb2 database, and it explicitly warns it fails if a project is already open. However, there is no stated guidance on when to prefer this over open_binary or the project_* graph tools, so the agent must infer the boundary.

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