Skip to main content
Glama

Verify an emitted app

verify_app
Read-onlyIdempotent

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

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": {
      "files": "<files>"
    },
    "name": "verify_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNoemit_app's share code; `appId` in .opointo/files.json
filesYeseach file written, hidden .opointo/files.json included: { path, bytes }, from the project root
configNo
toolchainNo
dependenciesNopackage.json keys

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / config / properties / connect
      Added value: +{
      +  "type": "string"
      +}
  2. Changed9 schema fields changed
    • addedInput schema / properties / config / properties / androidMinSdkVersion
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / config / properties / iosDeploymentTarget
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / config / properties / nativeModulesDir / description
      Previous value: -"package.json expo.autolinking; omit if unset"New value: +"package.json expo.autolinking"
    • addedInput schema / properties / config / properties / permissions
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / dependencies / description
      Previous value: -"package.json dependencies' keys"New value: +"package.json keys"
    • removedInput schema / properties / toolchain / properties / enableSceneSupport / description
      Removed value: -"app.json expo-build-properties ios.enableSceneSupport"
    • changedInput schema / properties / toolchain / properties / expoBuildProperties / description
      Previous value: -"INSTALLED expo-build-properties version; omit if absent"New value: +"INSTALLED expo-build-properties version"
    • changedInput schema / properties / toolchain / properties / expoSdk / description
      Previous value: -"the INSTALLED expo version, e.g. \"56.0.15\" (`npm ls expo`)"New value: +"INSTALLED expo version, e.g. \"58.0.19\""
    • changedInput schema / properties / toolchain / properties / xcode / description
      Previous value: -"`xcodebuild -version`, e.g. \"26.2\"; omit without Xcode"New value: +"`xcodebuild -version`; omit without Xcode"
  3. Changed7 schema fields changed
    • changedInput schema / properties / appId / description
      Previous value: -"the share code given to emit_app; `appId` in .opointo/files.json"New value: +"emit_app's share code; `appId` in .opointo/files.json"
    • addedInput schema / properties / config / properties / privacyPolicyUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / config / properties / release
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / files / description
      Previous value: -"each file written, the hidden .opointo/files.json included: { path, bytes }, path from the project root"New value: +"each file written, hidden .opointo/files.json included: { path, bytes }, from the project root"
    • changedInput schema / properties / files / items / properties / bytes / description
      Previous value: -"size in bytes on disk as `wc -c` reports, not the character count"New value: +"bytes on disk as `wc -c` reports, not characters"
    • changedInput schema / properties / files / items / properties / sha / description
      Previous value: -"optional; when sent, the byte check is skipped"New value: +"optional; replaces the byte check"
    • changedInput schema / properties / toolchain / properties / expoBuildProperties / description
      Previous value: -"the INSTALLED expo-build-properties version; omit if absent"New value: +"INSTALLED expo-build-properties version; omit if absent"
  4. Changed1 schema field changed
    • addedInput schema / properties / config / properties / sources
      Added value: +{
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / toolchain / properties / lastBuildFingerprint
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / toolchain / properties / nativeFingerprint
      Added value: +{
      +  "type": "string"
      +}
  6. 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"
      +}
  7. 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"
      +]
  8. 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"
  9. 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"
      +}
  10. Changed2 schema fields changed
    • addedInput schema / properties / toolchain / properties / expoBuildProperties
      Added value: +{
      +  "description": "the INSTALLED `expo-build-properties` version, e.g. \"57.0.21\"; omit if it is not installed",
      +  "type": "string"
      +}
    • changedInput schema / properties / toolchain / properties / expoSdk / description
      Previous value: -"the `expo` version in package.json, e.g. \"56.0.15\""New value: +"the INSTALLED `expo` package version, e.g. \"56.0.15\" (`npm ls expo`)"
  11. Changed1 schema field changed
    • addedInput schema / properties / toolchain
      Added value: +{
      +  "properties": {
      +    "enableSceneSupport": {
      +      "description": "app.json → expo-build-properties → ios.enableSceneSupport",
      +      "type": "boolean"
      +    },
      +    "expoSdk": {
      +      "description": "the `expo` version in package.json, e.g. \"56.0.15\"",
      +      "type": "string"
      +    },
      +    "xcode": {
      +      "description": "the version from `xcodebuild -version`, e.g. \"26.2\". iOS only; omit on a machine without Xcode",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  12. Changed3 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"what you actually wrote: { path, bytes } per file, path relative to the project root. Add `sha` for an exact check on a specific file."New 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."
    • addedInput schema / properties / files / items / properties / bytes / description
      Added value: +"size in bytes on disk, as `wc -c` reports"
    • addedInput schema / properties / files / items / properties / sha / description
      Added value: +"optional; when present it is authoritative and the byte check is skipped for that file"
  13. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is to add operational context, which it does: a subscription prerequisite and the full set of validations performed. Knowing that it inspects the expo-router config merge, the installed Xcode toolchain, and native-rebuild staleness tells an agent exactly what class of problems this surfaces. It does not say whether the call is fast or expensive, nor what form the findings take.

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?

One front-loaded sentence: prerequisite first, then the enumerated checks. No filler or restatement of the title. The telegraphic style ("expo-router's config merge", "absent packages") is dense but each clause carries a distinct check.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of explaining what comes back, and it does not — an agent cannot tell whether findings are a boolean, a list of issues, or per-check status codes, which is the single most important thing for a verification tool. Combined with 60% schema coverage on five parameters including nested config and toolchain objects, the definition is workable but leaves gaps an agent must discover by calling it.

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 coverage is 60% with nested objects, and the description adds no parameter information whatsoever — files, appId, config, toolchain, and dependencies are never mentioned. The schema itself does decent work (appId is tied to emit_app's share code, bytes are clarified as `wc -c` output rather than characters), which justifies a baseline 3, but roughly 40% of the surface is undocumented in both places, so the description leaves real compensation on the table.

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 ("Checks an emitted app before a build") and then enumerates the concrete checks performed: missing files, altered verbatim files, absent packages, expo-router config merge, Xcode buildability, native rebuild need. That level of specificity distinguishes it from emit_app (which produces the app) and from the code-level checkers among the siblings. It stops short of naming any sibling explicitly, so differentiation is inferred rather than stated.

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?

"before a build" gives useful timing context and "Needs a subscription" flags a prerequisite, so the usage window is implied. There is no explicit when-not guidance, no mention of what to do if verification fails, and no reference to emit_app or any sibling as an alternative, even though the appId parameter ties it directly to emit_app output.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources