Skip to main content
Glama

Xonta MAX

max_check_ad_post

Read-onlyIdempotent

Check an ad post for MAX against Russian ad marking rules: the 'Реклама' label at the top, advertiser details (name and INN/OGRN or a site), an erid token in the link or text, the A+ mark for channels over 10,000 subscribers, and the 4000-character limit. A hint, not legal advice; ORD registration is not checked.

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": {
      "text": "<text>"
    },
    "name": "max_check_ad_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textYesAd post text as it will be published
linksNoLinks used in buttons or elsewhere, if not in the text
advertiser_siteNoSite with the advertiser's details, if they are not in the text
channel_has_a_plusNoWhether the channel has the A+ mark (RKN registry)
channel_subscribersNoSubscribers of the channel where it goes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating what is verified and explicitly disclaiming two things (legal advice, ORD registration), but it never says what the response contains or how failures are surfaced, which matters here since 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.

Conciseness5/5

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

A single front-loaded sentence lists the checks compactly, followed by a one-line caveat that earns its place by bounding liability and scope. No filler or restated field names.

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?

For a read-only rule-checker with six fully documented parameters, the description covers input meaning and scope thoroughly. The gap is the return shape — with no output schema, an agent cannot know whether it receives per-rule pass/fail results or a summary, which is a modest but real omission.

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?

Schema coverage is 100%, so baseline would be 3; the description goes further by tying checks to specific inputs — erid in link or text (links param), advertiser name/INN/OGRN or site (advertiser_site), A+ mark and subscriber count for channels over 10,000 (channel_has_a_plus, channel_subscribers). This explains why those optional parameters exist, not just what they are.

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 ('Check an ad post') plus exact domain ('Russian ad marking rules') and enumerates the five concrete checks performed. This clearly separates it from siblings such as max_validate_message or max_lint_code without needing their schemas.

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

Usage Guidelines4/5

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

Implies the usage context (verifying an ad post before publication against marking rules) and adds an explicit exclusion: 'ORD registration is not checked' and 'A hint, not legal advice.' It does not, however, name an alternative tool or state when not to call it beyond that scope note.

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.