Skip to main content
Glama

ad-o-matic

adomatic_network_status

Read-onlyIdempotent

Query live Ad-o-matic Genesis Pool availability (first 50 store-verified published apps earn permanent Genesis Founding priority in P2P rotation and permanent directory listing, max 3 Genesis slots per developer), active peer count, and protocol rules.

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. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description only needs to add domain context; it does that by spelling out the Genesis Pool rules: the first 50 store-verified published apps, the max of 3 slots per developer, and the permanent priority and listing benefits. It still does not state how fresh the 'live' data is or what the response contains, which keeps it from 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, but the long embedded parenthetical about Genesis rules sits between 'availability' and 'active peer count, and protocol rules', so that list of returned items is harder to parse. The main verb and first resource are front-loaded, but the mid-sentence rule block hurts readability.

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?

This is a zero-parameter read tool with no output schema, so the description carries most of the burden of explaining what the tool returns. It lists the three kinds of results and the rules that govern them, which is enough context to call the tool correctly, though the shape and freshness of the returned data could still be more explicit.

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 there is no parameter meaning for the description to supply. The baseline score of 4 applies, and the description does not miss any needed argument semantics.

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 ('Query live Ad-o-matic Genesis Pool availability'), then names two more resources it returns: active peer count and protocol rules. This clearly separates it from the sibling mutation and verification tools (onboard_app, verify_integration, get_integration), though it never explicitly says so, so it falls short of a 5.

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?

The description does not say when an agent should call this tool instead of the siblings, nor does it state any prerequisite or precondition (for example, 'call before onboard_app to check remaining Genesis slots'). At most, the Genesis rules imply a use case, but the description never spells it out; the caller must infer it.

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