Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

jar_search_opcodes

Search bytecode opcode patterns in .class files to find code for modding Java-based games, aiding in patching or analysis.

Instructions

Search for bytecode opcode patterns in .class files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "pattern": "<pattern>"
    },
    "name": "jar_search_opcodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYesOpcode pattern to search for
session_idYesSession ID
file_filterNoOptional file filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether the operation is read-only, whether the search is scoped to the given session's loaded jars, how matching is performed, or whether results are capped. Only the surface intent is conveyed.

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, front-loaded sentence with no padding or redundancy. It is efficient, though it is arguably too terse for a tool with several ambiguous siblings.

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 three-parameter search tool with fully described parameters and no output schema, the description is minimally adequate. However, given the dense cluster of near-identical search siblings, the absence of any disambiguation or result-shape hint leaves a meaningful gap.

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 pattern, session_id, and file_filter are already documented in the schema; the description adds no extra meaning such as pattern syntax, whether file_filter supports globs/regex, or how patterns are matched against opcodes. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource: searching bytecode opcode patterns within .class files. It is clear on its own, but it does not distinguish itself from the close sibling jar_search_bytecode (or jar_search), leaving the agent to guess which search variant applies.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the many overlapping search siblings (jar_search, jar_search_bytecode, pattern_scan, search_code). No prerequisites, exclusions, or alternative routing are given.

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