Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Validate ads.txt / app-ads.txt

web-technology_ads-txt-validate
Read-onlyIdempotent

Validate ads.txt records and variables, optionally cross-checking DIRECT seller IDs against sellers.json. Price $0.02 USDC. POST /api/v1/web-technology/ads-txt-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "adsTxt": "<adsTxt>"
    },
    "name": "web-technology_ads-txt-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
adsTxtYesadsTxt, string, length 1 to 500000. Required.
ownDomainNoownDomain, string. Optional.
sellersJsonNosellersJson, object. Optional.

Output Schema

NameRequiredDescriptionDefault
errorsNoerrors. Array.
recordsNorecords. Number.
sourcesNosources. Array.
warningsNowarnings. Array.
variablesNovariables. Object.
limitationsNolimitations. Array.
sellerCrossCheckNosellerCrossCheck. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description goes beyond this by disclosing the price ($0.02 USDC), the HTTP method and endpoint, and the critical fact that an unpaid call returns payment terms without executing. This is valuable behavioral context for a paid API.

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?

Three sentences, each front-loaded with essential information: purpose, price, and unpaid-call behavior. No redundant or filler text; the progression from core function to payment details is logical and efficient.

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?

Given the presence of an output schema, the description need not explain return values. It covers payment terms, endpoint, and the unpaid-call behavior, which are critical for invocation. A minor gap is that it does not mention the optional ownDomain parameter's purpose, but the schema and annotations together provide sufficient context for correct use.

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 description coverage is 100%, so the structured fields already document each parameter. The description still adds meaning by explaining that sellersJson is used to cross-check DIRECT seller IDs, giving semantic purpose beyond the schema's technical definition. It does not explain ownDomain, but the schema covers that.

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 states a specific verb ('Validate') and resource ('ads.txt records and variables'), and adds the optional cross-checking of DIRECT seller IDs against sellers.json. It clearly distinguishes the tool from sibling validation tools like security-txt-validate by naming the target file, though it does not explicitly name a sibling to route away from.

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 description implies usage by mentioning the optional cross-check with sellers.json, but it offers no explicit when-to-use guidance, no alternatives, and no exclusions. An agent can infer the tool's role from its name and description, but must rely on other context to decide between this and similar validation endpoints.

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