Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_playerprefs

Retrieve Unity PlayerPrefs values from the Windows registry using a game's company and product name, with an optional key filter to narrow results.

Instructions

Read Unity PlayerPrefs from Windows registry.

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": {
      "company_name": "<company_name>",
      "product_name": "<product_name>"
    },
    "name": "read_playerprefs"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOptional key filter
company_nameYesCompany name from PlayerSettings
product_nameYesProduct name from PlayerSettings

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 burden. It discloses the Windows-registry backing store, which is useful, but says nothing about read-only guarantees, behavior when PlayerPrefs are absent, permissions, or return format for a tool that crosses into OS-level state.

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 zero filler. It is well structured but so terse that it borders on underspecification rather than being optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description should clarify what is returned (key/value pairs?) and what happens on a miss. None of that is present, leaving meaningful gaps for correctness of invocation.

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 company_name, product_name and the optional key filter are already documented in the schema. The description adds nothing beyond that, which matches the baseline 3 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?

States a specific verb ('Read') and resource ('Unity PlayerPrefs'), and adds the storage location (Windows registry). No sibling tool touches PlayerPrefs, so no differentiation is needed, though it also doesn't differentiate itself from generic read tools.

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 guidance on when to use this tool versus alternatives, nor any prerequisites such as needing PlayerSettings values or a valid installed game. The agent is left to infer usage entirely from the name.

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