Skip to main content
Glama

Ad-o-matic Free Mobile App Cross-Promotion

adomatic_network_status

Read-onlyIdempotent

Retrieve live network-wide Ad-o-matic pool metrics and Genesis Member slot availability (first 50 store-verified apps receive permanent founding priority, max 3 per developer). Read-only; takes no parameters and never mutates state. Returns genesisSpotsTotal, genesisSpotsClaimed, genesisSpotsRemaining, maxGenesisSpotsPerDeveloper, registeredAppsCount, distinctDeveloperGroups, bannerTestPeriodDays, and genesisMembers. Usage: call to check overall network health, active peer count, or open Genesis slots before onboarding. To inspect a specific app's integration checklist, call adomatic_verify_integration instead.

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_network_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'read-only; never mutates state' mostly restates structured data. What the description adds beyond that is real domain context: the Genesis program rules (first 50 store-verified apps, max 3 per developer) and an enumeration of returned fields, which matters because there is no output schema.

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?

Information is front-loaded: purpose, then safety, then return fields, then usage and the alternative. It is dense but not padded; the only waste is the redundant 'never mutates state' restatement of annotations, and the bare field list is compact rather than explained.

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, listing genesisSpotsTotal, genesisSpotsClaimed, genesisSpotsRemaining, maxGenesisSpotsPerDeveloper, registeredAppsCount, distinctDeveloperGroups, bannerTestPeriodDays, and genesisMembers is the main completeness win. It stops short of explaining ambiguous fields such as distinctDeveloperGroups or bannerTestPeriodDays, but for a no-parameter read tool this is close to sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so parameter semantics is a baseline-4 case; there is nothing for the description to disambiguate. The explicit 'takes no parameters' note correctly signals an agent needs no argument assembly.

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?

The description leads with a specific verb-resource pair ('Retrieve live network-wide Ad-o-matic pool metrics and Genesis Member slot availability') and enumerates the concrete data domains. It also names the sibling it is not (adomatic_verify_integration), so an agent can distinguish them without opening either 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?

It gives an explicit usage clause ('call to check overall network health, active peer count, or open Genesis slots before onboarding') plus a routing exclusion to adomatic_verify_integration for per-app checklists. Both the when and the when-not are stated.

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.