Skip to main content
Glama

Verify an emitted app

verify_app
Read-onlyIdempotent

Needs a subscription. Checks an emitted app before it is built: missing files, altered copy-verbatim files, absent packages, the config merge expo-router needs, and whether the installed Xcode can build the project. Takes the files written with byte sizes, package.json dependencies, project config and toolchain versions.

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. 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"
      +]
  2. 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"
  3. 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"
      +}
  4. 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`)"
  5. 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"
      +}
  6. 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"
  7. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds value beyond them by disclosing the subscription requirement and the pre-build validation role, but says nothing about how findings are reported or whether it fails fast vs. collecting all issues.

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?

Two dense sentences with no filler; the subscription prerequisite and pre-build framing are front-loaded. The long comma-separated checklist is information-rich but slightly compressed, which is acceptable for the amount it conveys.

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?

For a 5-parameter tool with nested objects and no output schema, the description covers inputs, precondition, and the nature of the checks performed, which implicitly describes what the caller learns back. It stops short of describing result shape or error behavior, a minor gap given no output schema exists.

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% and the description only restates the input families (files with byte sizes, package.json dependencies, project config, toolchain versions) without adding format or semantic detail beyond what the schema documents. Under the high-coverage baseline rule this is a straight 3.

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 precise verb and resource ('Checks an emitted app before it is built') and enumerates the concrete failure classes it detects (missing files, altered copy-verbatim files, absent packages, expo-router config merge, Xcode buildability). This clearly separates it from siblings like emit_app, check_snippet and propose_app.

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?

Gives the operative timing context — run before the app is built — and the gating prerequisite ('Needs a subscription'), which is exactly the kind of usage guidance an agent needs. It does not name alternatives or state when not to use it, so it stops short of a 5.

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