Skip to main content
Glama
Sign In

Mobiscroll

by com.mobiscroll
OverviewDiscussionsAdmin

Resolve Mobiscroll UI Environment

resolveEnvironment
Read-onlyIdempotent

Resolves which Mobiscroll framework and major version a project uses, from the contents of its package.json. This server runs remotely and has no access to the local filesystem, so the file contents are passed in as packageJsonContent. Returns the framework and major version that the other tools in this server take as arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkNoOnly for the no-package.json path, and only together with noPackageJsonReason. Do NOT use this to skip reading an existing package.json - passing framework without noPackageJsonReason is rejected.
packageJsonContentNoREQUIRED (raw file text). The full raw content of the project's package.json - the repository root, or the nearest one above the file you are editing. Read the file from the workspace and pass its content here. In a monorepo, use the package.json that declares the @mobiscroll/* dependency.
noPackageJsonReasonNoSet ONLY after searching the workspace and confirming NO package.json exists (repo root or any parent of the edited file). 'cdn' = Mobiscroll loaded via a script tag; 'no-package-json-found-after-search' = you searched and found none. Required (with framework) to use the no-package.json path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / packageJsonContent / description
      Previous value: -"REQUIRED (raw file text). The full raw content of the project's package.json - the repository root, or the nearest one above the file you are editing. Read the file from the workspace and pass its content here."New value: +"REQUIRED (raw file text). The full raw content of the project's package.json - the repository root, or the nearest one above the file you are editing. Read the file from the workspace and pass its content here. In a monorepo, use the package.json that declares the @mobiscroll/* dependency."
    • removedInput schema / properties / workingDirectory
      Removed value: -{
-  "description": "stdio mode only. Path to the repository to analyze (defaults to current directory). Ignored over HTTP, where the server cannot access the local filesystem.",
-  "type": "string"
-}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: the server runs remotely with no local filesystem access, which explains why file contents must be passed in. It does not, however, describe failure modes or what happens when the content is unrecognized.

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?

Three tightly written sentences, front-loaded with the purpose and followed by the constraint and the return value. No filler, though the return-value sentence partly overlaps with what the purpose sentence already implies.

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

Completeness4/5

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

With no output schema, the description correctly explains the return value (framework and major version) and the remote-server constraint. The full no-package.json fallback path is left to the schema, which is acceptable since the schema documents it explicitly.

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 the schema already fully documents all three parameters including the enum gating. The description adds the 'no local filesystem' rationale for packageJsonContent, but its monorepo guidance largely restates the schema. Baseline 3 is appropriate 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Resolves which Mobiscroll framework and major version a project uses, from the contents of its package.json') and names the exact input it consumes and the output it produces. It is clearly distinguishable from the sibling resolveConnectEnvironment by targeting Mobiscroll framework/version rather than Connect environment.

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?

Explains the operative condition for use (project has a package.json whose contents describe the framework/version) and gives an actionable instruction ('Read the file from the workspace and pass its content here'). It does not explicitly name an alternative path for the no-package.json case, though the schema does.

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

All Mobiscroll toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources