Skip to main content
Glama

ad-o-matic

adomatic_verify_integration

Read-onlyIdempotent

Verify an app's Ad-o-matic integration status, Genesis Member eligibility checklist (50 founding spots total), remaining Genesis spots, and matched customer-group segments (read-only).

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 banner copy to preview audience segment matching
packageNameYesAndroid applicationId / packageName or iOS 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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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), and '(read-only)' in the description merely restates that. The description does add genuinely new behavioral context: eligibility is tied to a hard cap of 50 founding spots, so results are time-sensitive and a spot count is returned. It stops short of explaining what the checklist contains or how eligibility is decided.

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 verb and resource first, then the enumerated outputs. It is dense but each clause earns its place as a returned item. The lone redundancy is '(read-only)', which duplicates the annotations.

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?

With no output schema, the description does useful work by naming the four return categories, which is more than most. However, the 'Genesis Member eligibility checklist' is never unpacked, and there is no indication of what a non-integrated app returns or how spot counts relate to eligibility, leaving the agent to guess at the response shape.

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% and the targetAudience parameter carries a long, example-rich description, so the schema does the heavy lifting. The only description-side contribution is 'matched customer-group segments', which hints at how targetAudience and bannerText are used but adds no syntax or behavior beyond the schema. 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?

The description opens with a specific verb and resource ('Verify an app's Ad-o-matic integration status') and enumerates the four things the call surfaces: status, Genesis eligibility checklist, remaining Genesis spots, and matched segments. That is far more informative than the title alone. It does not, however, distinguish itself from the closely named sibling 'adomatic_get_integration', leaving the boundary between the two implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. A reader can infer this is a post-integration check, but nothing says whether to call it before or after 'adomatic_get_integration' or 'adomatic_onboard_app', which is the main selection risk given the near-identical sibling name.

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