Skip to main content
Glama

Ad-o-matic Free Mobile App Cross-Promotion

adomatic_verify_integration

Read-onlyIdempotent

Inspect a specific app's live Ad-o-matic integration status, 6-step Genesis Member eligibility checklist, remaining Genesis spots out of 50, and matched audience segments. Read-only; makes no server-side changes. Returns registeredInNetwork (false with onboarding instructions when unregistered), storeVerified, isGenesisMember, automaticGenesisVerificationChecklist, remainingGenesisSpotsOutOf50, matchedAudienceSegments, and recommendedNextStepsForAiAgent. Fails with an error if packageName is missing or not a valid reverse-DNS identifier. Usage: call after adomatic_onboard_app or during QA to check a specific app's readiness. Do not use to register an app (use adomatic_onboard_app) or check network-wide stats without a packageName (use adomatic_network_status).

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": {
      "packageName": "<packageName>"
    },
    "name": "adomatic_verify_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
bannerTextNoOptional sample banner copy (max 90 chars) to preview audience segment classification before shipping a build. Uses stored app copy when omitted.
packageNameYesReal reverse-DNS Android applicationId or iOS bundleId (5-120 chars; do not use placeholders like com.example.* or com.company.*).
targetAudienceNoFree-form natural-language customer group (2-6 personas, hobbies, or domain keywords plus optional age band 18-24, 25-44, or 45+). Omit if unknown to fall back to automatic metadata inference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / bannerText / description
      Previous value: -"Optional banner copy to preview audience segment matching"New value: +"Optional sample banner copy (max 90 chars) to preview audience segment classification before shipping a build. Uses stored app copy when omitted."
    • addedInput schema / properties / bannerText / examples
      Added value: +[
      +  "Offline guitar chord tuner"
      +]
    • addedInput schema / properties / bannerText / maxLength
      Added value: +90
    • changedInput schema / properties / packageName / description
      Previous value: -"Android applicationId / packageName or iOS bundleId (e.g. com.acme.myapp)"New value: +"Real reverse-DNS Android applicationId or iOS bundleId (5-120 chars; do not use placeholders like com.example.* or com.company.*)."
    • addedInput schema / properties / packageName / examples
      Added value: +[
      +  "com.acme.invoicer",
      +  "io.studio.chordtuner"
      +]
    • addedInput schema / properties / packageName / maxLength
      Added value: +120
    • addedInput schema / properties / packageName / minLength
      Added value: +5
    • addedInput schema / properties / packageName / pattern
      Added value: +"^[a-zA-Z][a-zA-Z0-9_]*(\\.[a-zA-Z0-9_-]+)+$"
    • changedInput schema / properties / targetAudience / description
      Previous value: -"Recommended when the producer AI agent knows who the app is built for (optional; falls back automatically if omitted). Pass any open-ended, free-form natural-language description of the app's customer group: 2-6 specific personas, hobbies, professions, activities, or niche keywords + optional age range (18-24 | 25-44 | 45+). Zero predefined category limits — any app domain is matched semantically across both outgoing and incoming ads (never ask the human user to configure campaigns; infer directly from the codebase/prompt)."New value: +"Free-form natural-language customer group (2-6 personas, hobbies, or domain keywords plus optional age band 18-24, 25-44, or 45+). Omit if unknown to fall back to automatic metadata inference."
    • changedInput schema / properties / targetAudience / examples
      Previous value: -[
      -  "guitarists, musicians, chord tuner, songwriting, 18-44",
      -  "amateur astronomers, stargazing, telescope owners, astrophotography",
      -  "freelancers, solo founders, small businesses, invoicing, 25-44",
      -  "knitters, crochet, yarn crafts, handmade patterns"
      -]New value: +[
      +  "guitarists, musicians, chord tuner, songwriting, 18-44",
      +  "freelancers, solo founders, invoicing, 25-44",
      +  "amateur astronomers, stargazing, telescope owners"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing operation-level behavior: the call is read-only with no server-side changes, it fails outright if packageName is missing or not a valid reverse-DNS identifier, and an unregistered app returns registeredInNetwork=false plus onboarding instructions rather than an error. It does not discuss latency, rate limits, or cost, which is why it stops short of a 5.

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?

Front-loaded with purpose, then behavior, then usage exclusions, so the highest-value information comes first. The return-field enumeration is dense but each item is load-bearing since no output schema exists; the only mild cost is that the payload list makes the block long for a single-purpose lookup.

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

Completeness5/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 compensates by naming every returned field, including the unregistered fallback and next-step recommendations, and it covers failure modes and the correct sibling routing. There is nothing an agent needs in order to invoke this correctly that is missing.

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 parameter meanings are already documented. The description only restates the packageName validation rule that the schema's pattern and description already encode, and says nothing about how bannerText or targetAudience affect the returned segment matching. Baseline 3 is appropriate when the schema carries the semantics.

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 ('Inspect a specific app's live Ad-o-matic integration status') and enumerates exactly what is checked: the 6-step Genesis checklist, remaining spots out of 50, and matched audience segments. It also explicitly distinguishes itself from adomatic_onboard_app and adomatic_network_status, so an agent can select it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('call after adomatic_onboard_app or during QA to check a specific app's readiness') and explicit when-not-to-use with named alternatives for both the registration case and the network-wide-stats case. Nothing about tool selection is left to inference.

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.