Skip to main content
Glama

opointo

by com.opointo
OverviewDiscussionsAdmin

Verify an emitted app

verify_app
Read-onlyIdempotent

Needs a subscription. Checks an emitted app before it is built: missing files, altered verbatim files, absent packages, the expo-router config merge, whether the installed Xcode can build it, and whether a change needs a new native build.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNothe share code given to emit_app; `appId` in .opointo/files.json
filesYeseach file written, the hidden .opointo/files.json included: { path, bytes }, path from the project root
configNo
toolchainNo
dependenciesNopackage.json dependencies' keys

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / config / properties / sources
      Added value: +{
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / toolchain / properties / lastBuildFingerprint
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / toolchain / properties / nativeFingerprint
      Added value: +{
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / properties / config / properties / icon
      Added value: +{
+  "description": "app.json",
+  "type": "string"
+}
    • addedInput schema / properties / config / properties / monochromeImage
      Added value: +{
+  "description": "app.json android.adaptiveIcon",
+  "type": "string"
+}
    • addedInput schema / properties / config / properties / supportsTablet
      Added value: +{
+  "description": "app.json ios",
+  "type": "boolean"
+}
  4. Changed3 schema fields changed
    • changedInput schema / properties / appId / description
      Previous value: -"the share code given to emit_app"New value: +"the share code given to emit_app; `appId` in .opointo/files.json"
    • changedInput schema / properties / files / description
      Previous value: -"each file written: { path, bytes }, path from the project root"New value: +"each file written, the hidden .opointo/files.json included: { path, bytes }, path from the project root"
    • changedInput schema / required
      Previous value: -[
-  "appId",
-  "files"
-]New value: +[
+  "files"
+]
  5. Changed14 schema fields changed
    • changedInput schema / properties / appId / description
      Previous value: -"the share code you passed to emit_app"New value: +"the share code given to emit_app"
    • changedInput schema / properties / config / properties / moduleSuffixes / description
      Previous value: -"tsconfig compilerOptions.moduleSuffixes"New value: +"tsconfig compilerOptions"
    • changedInput schema / properties / config / properties / nativeModulesDir / description
      Previous value: -"package.json expo.autolinking.nativeModulesDir; omit if unset. Checked when the recipe ships a native module in src/modules. Unset, that module is never linked and the app crashes on Android at first render"New value: +"package.json expo.autolinking; omit if unset"
    • changedInput schema / properties / config / properties / plugins / description
      Previous value: -"app.json plugins"New value: +"app.json"
    • changedInput schema / properties / config / properties / scheme / description
      Previous value: -"app.json scheme"New value: +"app.json"
    • changedInput schema / properties / config / properties / userInterfaceStyle / description
      Previous value: -"app.json userInterfaceStyle"New value: +"app.json"
    • changedInput schema / properties / dependencies / description
      Previous value: -"the keys of package.json's dependencies"New value: +"package.json dependencies' keys"
    • changedInput schema / properties / files / description
      Previous value: -"what you actually wrote: { path, bytes } per file, path relative to the project root. `bytes` must be the file's size in BYTES on disk (what `wc -c` reports), not its character count — the two differ for any file containing a non-ASCII character."New value: +"each file written: { path, bytes }, path from the project root"
    • changedInput schema / properties / files / items / properties / bytes / description
      Previous value: -"size in bytes on disk, as `wc -c` reports"New value: +"size in bytes on disk as `wc -c` reports, not the character count"
    • changedInput schema / properties / files / items / properties / sha / description
      Previous value: -"optional; when present it is authoritative and the byte check is skipped for that file"New value: +"optional; when sent, the byte check is skipped"
    • changedInput schema / properties / toolchain / properties / enableSceneSupport / description
      Previous value: -"app.json → expo-build-properties → ios.enableSceneSupport"New value: +"app.json expo-build-properties ios.enableSceneSupport"
    • changedInput schema / properties / toolchain / properties / expoBuildProperties / description
      Previous value: -"the INSTALLED `expo-build-properties` version, e.g. \"57.0.21\"; omit if it is not installed"New value: +"the INSTALLED expo-build-properties version; omit if absent"
    • changedInput schema / properties / toolchain / properties / expoSdk / description
      Previous value: -"the INSTALLED `expo` package version, e.g. \"56.0.15\" (`npm ls expo`)"New value: +"the INSTALLED expo version, e.g. \"56.0.15\" (`npm ls expo`)"
    • changedInput schema / properties / toolchain / properties / xcode / description
      Previous value: -"the version from `xcodebuild -version`, e.g. \"26.2\". iOS only; omit on a machine without Xcode"New value: +"`xcodebuild -version`, e.g. \"26.2\"; omit without Xcode"
  6. Changed1 schema field changed
    • addedInput schema / properties / config / properties / nativeModulesDir
      Added value: +{
+  "description": "package.json expo.autolinking.nativeModulesDir; omit if unset. Checked when the recipe ships a native module in src/modules. Unset, that module is never linked and the app crashes on Android at first render",
+  "type": "string"
+}
  7. 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 readOnly/idempotent/non-destructive, so safety is covered; the description adds real context beyond that: a subscription requirement and the fact that verification happens pre-build and can report whether a change requires a new native build. It stops short of describing the shape of the findings or how failures are surfaced.

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 the prerequisite first and the check list following. Every clause maps to an actual verification behavior, though the long comma series is dense and could be trimmed.

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 enumeration of checks effectively tells the agent what the response will cover (missing/altered files, packages, config merge, Xcode, native rebuild). Missing is any detail on result format or severity reporting, but for a read-only verification tool with rich parameter descriptions this is largely sufficient.

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 60% and the inputs are heavily nested (config, toolchain, files[].sha/bytes with source hints like `xcodebuild -version`), so the schema carries most of the semantic load. The description never names appId, files, config, toolchain, or dependencies, only implying them indirectly through the checks it lists; baseline 3 is appropriate.

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?

Specific verb (checks/verifies) plus a specific resource (an emitted app), and it enumerates exactly what is inspected: missing files, altered verbatim files, absent packages, expo-router config merge, Xcode buildability, native-rebuild need. This clearly separates it from emit_app (which produces the app) and check_snippet (a narrower check).

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?

"before it is built" gives a clear lifecycle cue for when to call it, and "Needs a subscription" states a prerequisite. It does not name alternatives or exclusions (e.g., when to prefer get_app_setup or check_snippet), so it falls short of explicit routing guidance.

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

All opointo toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources