Skip to main content
Glama

ad-o-matic

adomatic_get_integration

Read-onlyIdempotent

Get zero-dependency single-file SDK code for Android Jetpack Compose (HouseAdBanner.kt), iOS SwiftUI (HouseAdBanner.swift), Flutter (HouseAdBanner.dart), React Native (HouseAdBanner.tsx), or Hybrid Mobile WebView (ad-widget.js) and the 1-line free app cross-promotion snippet. Pass targetAudience (inferred from the app codebase/prompt) so ads reach the right customer group.

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": "adomatic_get_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoTarget app framework/platform SDK (android, ios, flutter, react-native, or web)
bannerTextNoOptional short benefit-driven ad text compiled into the app build (max 90 chars)
packageNameNoApp packageName or bundleId (e.g. com.acme.myapp)
targetAudienceNoRecommended 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).
includeFullSdkSourceNoSet true to return the full zero-dependency single-file SDK source code ready to write into the project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description is free to add context — and it does, describing what is returned (single-file zero-dependency SDK source per platform plus a cross-promo snippet) and the targeting effect of targetAudience. It stops short of noting any auth requirements, embedded keys, or rate limits.

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 sentences, front-loaded with the concrete deliverables and platform mapping, then the key targeting instruction. The long parenthetical file list is dense but each item is informative, and there is no filler.

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 appropriately names the returned artifacts and the platform-specific file names, and annotations cover the safety profile, so an agent has what it needs to call this correctly. Only the relationship to downstream verification remains unstated.

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 documents all five optional parameters in detail, including the targetAudience persona format and the includeFullSdkSource flag. The description reinforces the intent behind targetAudience but adds no format or behavioral detail beyond what the schema states, so baseline 3 applies.

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?

Uses a concrete verb ('Get') with a specific resource (zero-dependency single-file SDK code) and enumerates exact per-platform artifacts (HouseAdBanner.kt, .swift, .dart, .tsx, ad-widget.js) plus the 1-line cross-promo snippet. An agent can immediately tell this produces integration code; however, it never explicitly contrasts itself with siblings like adomatic_verify_integration, leaving the division of labor to inference.

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?

The only usage instruction is to pass targetAudience inferred from the app codebase/prompt rather than asking the user, which is genuinely useful guidance. There is no statement of when to call this versus adomatic_verify_integration or adomatic_onboard_app, and no prerequisites or follow-up flow described, so usage is implied rather than spelled out.

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