ppsspp-dfx

Overview Schema Source Related Servers Discussions Admin

ppsspp_list_addresses

Read-onlyIdempotent

List project address constants from addresses.yaml, with optional section filtering, to retrieve exact hex addresses without guessing.

Instructions

PURPOSE: List the project's known address constants from addresses.yaml — the single source of truth; never guess hex addresses.

USAGE: optional section filter; an unknown section returns an error listing the valid ones.

CONVERSION: IDA <-> PPSSPP address conversion is plain arithmetic — ppsspp_addr = ida_addr + (top_base.ppsspp - top_base.ida) (defaults 0x08804000 - 0x00000000). ppsspp_convert_address was un-tooled in v0.1.6. BEHAVIOR: READ-ONLY. Int values ≥0x1000 are returned as hex strings that can be pasted straight into address parameters.

RETURNS: {sections, count, section_filter}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`section`	No	Optional section filter (e.g. 'known_functions', 'state_probes', 'top_base'). If omitted, returns all sections.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`sections`	Yes
`section_filter`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so 'READ-ONLY' is largely redundant, but the description adds genuinely new behavior: ints ≥0x1000 are returned as hex strings safe to paste into address parameters, and the exact IDA↔PPSSPP conversion arithmetic (with the v0.1.6 note that convert_address no longer exists). Those are real operational facts an agent cannot get from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Labeled PURPOSE/USAGE/CONVERSION/BEHAVIOR/RETURNS sections are front-loaded and each carries usable content; nothing is padding. It is denser than strictly needed for a one-parameter list tool — the conversion formula and version-history note are slightly tangential — but they are relevant and compact.

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?

An output schema exists, and the description still summarizes the return shape ({sections, count, section_filter}) and the hex-string formatting of values. With safety covered by annotations, filtering, error behavior, conversion, and return content all addressed, an agent has everything needed to call and interpret this tool.

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?

Schema coverage is 100% and the schema already documents the section parameter with examples, so the baseline is 3. The description adds error semantics the schema lacks: an unknown section fails with an error enumerating valid sections, which changes how an agent should recover from a bad filter.

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?

States a specific verb (list), a specific resource (address constants), and the authoritative source (addresses.yaml), plus the explicit anti-goal 'never guess hex addresses'. An agent can distinguish this from memory-map/scan/read-memory siblings without opening any schema.

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?

Gives clear context for use (the source of truth for addresses, used before supplying address parameters) and documents the optional section filter and its error behavior. It does not explicitly name which sibling to use instead for related lookups (e.g. memory_map vs. this list), so it stops short of full routing guidance.

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