ppsspp-dfx

Overview Schema Source Related Servers Discussions Admin

ppsspp_reload_scripts

Idempotent

Reload the script manifest YAML and clear cached script modules to apply script changes without restarting the PPSSPP DFX server.

Instructions

PURPOSE: Manually reload the script manifest YAML and clear the script module cache.

USAGE: No parameters.

BEHAVIOR: MUTATING. Re-reads the manifest file and invalidates cached script modules. Reversible: re-reading an unchanged file produces an equal registry. When the exposed tool set ACTUALLY changes (tools added or removed), the server notifies the client with a tool-list-changed notification so cached tools/list results are invalidated; a no-op reload sends nothing.

RETURNS: {reloaded_count, exposed_count, manifest_path, scripts: [ScriptEntryView...]}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`scripts`	Yes	All entries after reload (post-reload snapshot).
`exposed_added`	Yes	Script names newly registered by this reload's sync.
`exposed_count`	Yes	Number of exposed scripts (exposed=true) after reload.
`manifest_path`	Yes	Absolute path to the manifest YAML.
`reloaded_count`	Yes	Total script entries after reload (manifest-wide).
`exposed_removed`	Yes	Script names unregistered by this reload's sync.
`restart_required`	Yes	True when some registration changes could not be applied at runtime (SDK limitation) and a server restart is needed to fully reconcile exposed tools.
`exposed_registered`	Yes	Number of exposed scripts ACTUALLY registered as dynamic tools after the reload sync (declared != registered is now surfaced instead of silently diverging).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.7Oct 7, 2026

changedOutput schema / properties / exposed_registered / description

Previous value: -"Number of exposed scripts ACTUALLY registered as dynamic tools after the reload sync (F4/F5: declared != registered is now surfaced instead of silently diverging)."New value: +"Number of exposed scripts ACTUALLY registered as dynamic tools after the reload sync (declared != registered is now surfaced instead of silently diverging)."

First observedv0.1.0Sep 16, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well past the annotations by disclosing that it re-reads the manifest, invalidates the module cache, is reversible because an unchanged file yields an equal registry, and that a tool-list-changed notification is emitted only when the exposed set actually changes. Annotations only say it is mutating, idempotent and non-destructive; this adds the observable side effects.

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?

Labeled PURPOSE/USAGE/BEHAVIOR/RETURNS sections front-load the essential information, and the conditional notification detail is packed into one dense sentence without padding. Every sentence contributes.

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; annotations cover the safety profile and the description adds the cache/manifest semantics and notification behavior. Nothing an agent needs to call this mutation correctly is missing.

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 (schema coverage 100%), and the description correctly states 'No parameters', so there is nothing further to document. Baseline 4 applies for a parameterless tool.

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?

States a specific verb and resource ('reload the script manifest YAML and clear the script module cache'), which is far more than a restatement of the name. It does not, however, explicitly contrast itself with siblings like ppsspp_list_scripts or ppsspp_run_script, so an agent must infer the distinction.

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: No parameters' describes invocation mechanics, not when to reach for this tool. There is no statement of when a reload is warranted (e.g., after the manifest changes) or how it relates to list_scripts/run_script, leaving usage implied rather than guided.

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