Skip to main content
Glama
AstralVoidZ
by AstralVoidZ

ppsspp_search_disasm

Read-onlyIdempotent

Search disassembly for a substring across a memory range, wrapping around memory when needed, and collect every matching instruction with its address, name, and parameters.

Instructions

PURPOSE: Loop-search disassembly for a substring, collecting matching instructions with context.

USAGE: session_id + match (a leading '$' is stripped); start address; end=0 wraps the search around the whole region; max_results default 100.

BEHAVIOR: READ-ONLY.

RETURNS: {address, match, end, results[{address, text, name, params}], text}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd address for the search range, as a hex string (e.g. '0x08810000'). If 0 or equal to `address`, PPSSPP performs a loop search (wraps around memory).0x0
matchYesCase-insensitive substring to search for in the disassembly text (e.g., 'jal', 'addiu', 'lw r5'). May include '$' register prefix (e.g. 'jr $ra') — automatically stripped before forwarding to PPSSPP (PPSSPP register names have no '$' prefix). Required by PPSSPP's memory.searchDisasm event.
addressYesStarting address for the disassembly search, as a hex string (e.g. '0x08804000').
session_idYesActive session ID.
max_resultsNoMaximum number of matches to collect (default 100). PPSSPP returns only the first match per call; the tool loops from each match address+4 until no more matches, this cap is reached, or a loop is detected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd address, hex string. '0x00000000' or equal to `address` means loop search.
textYesUnified multi-line text representation. Each line is '0x{ADDR:08X}: {text}'.
matchYesCase-insensitive substring matched.
addressYesStarting address for the search, hex string (e.g. '0x08804000').
resultsYesList of disasm line dicts (address / text / name / params).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description repeats 'READ-ONLY.' It also discloses loop/wrap behavior and match collection, but these details are already in the schema's parameter descriptions, so the description adds little new behavioral context beyond the annotations.

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?

The description uses four labeled one-line sections (PURPOSE, USAGE, BEHAVIOR, RETURNS) and front-loads the purpose. Every line earns its place, and there is no fluff or redundant elaboration.

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 the detailed input schema covering all parameters, the read-only/idempotent annotations, and an output schema present, the description gives enough operational context including defaults, wrap behavior, and return envelope. An agent has all needed information to select and invoke this tool 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 every parameter already has thorough semantic explanation (e.g., end=0 wrap behavior, '$' stripping, max_results loop mechanism). The description's USAGE line merely summarizes these details without adding further meaning, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Loop-search disassembly for a substring, collecting matching instructions with context.' This makes the tool's function immediately clear and inherently differentiates it from siblings like ppsspp_disassemble (one-shot disassembly) and ppsspp_memory_info_search (searching memory values rather than disassembly text).

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?

The USAGE section provides concrete invocation guidance: required session_id and match, leading '$' stripping, start address, end=0 wrap-around, and max_results default. It does not explicitly name alternatives or state when not to use this tool, but the context is clear enough to proceed.

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