vastlint
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| explain_ruleA | Get full details for a specific VAST validation rule: description, spec reference, severity, what triggers it, and how to fix it. Use rule IDs from list_rules. This is the primary tool for understanding and fixing VAST issues flagged by validate_vast. |
| fix_vastA | Auto-fix a VAST XML tag. Applies all deterministic, safe fixes: HTTP → HTTPS upgrades (including SIMID HTTP://), SIMID apiFramework casing, true-intent variableDuration, missing SIMID type="text/html", and removal of deprecated attributes. Does not rewrite javascript: URLs or an existing type MIME. Returns the repaired XML, a list of every fix applied (rule ID + description + path), and any remaining issues that require manual intervention. Always re-validate the returned xml with validate_vast to confirm no errors remain. |
| get_adcp_capabilitiesA | AdCP protocol discovery. Returns the AdCP version, supported protocols, and governance capabilities of this vastlint agent. Call this first when integrating vastlint into an AdCP creative pipeline — it declares which VAST creative features can be evaluated (spec compliance, HTTPS enforcement, wrapper depth). Part of the Ad Context Protocol (AdCP 3.0) specification. |
| inspect_vastA | Follow a VAST wrapper chain from a URL, fetching and validating every hop. Returns each hop as a structured object: AdSystem, AdTitle, Duration, impression count, tracking event count, media files (with MIME type, dimensions, bitrate, URL), companion count, and per-hop validation issues. The final InLine hop contains the actual creative. Use this to debug wrapper chains, verify creative assets, or analyse a full ad delivery path. max_depth defaults to 5 per IAB recommendation. |
| list_rulesA | List the full catalog of validation rules available in vastlint. Covers VAST 2.0-4.4, VMAP 1.0, and DAAST 1.0/1.1. Returns rule IDs, default severities, descriptions, and the external standard each rule is derived from (e.g. "VAST spec", "VAST XSD", "IAB VMAP", "IAB DAAST", "RFC 3986", "inferred"). Call this once and cache the result — the catalog is static. Use rule IDs from this list with explain_rule for full details and fix guidance. |
| validate_vastA | Validate an IAB ad tag XML document. Accepts VAST 2.0-4.4, VMAP 1.0, and DAAST 1.0/1.1. The document type is auto-detected from the root element. Returns all issues found with severity, rule ID, location, and spec reference. A document is valid when errors == 0, regardless of warning or info count. Use wrapper_depth when validating a VAST document inside a wrapper chain. |
| validate_vast_urlA | Fetch an IAB ad tag XML document from a URL and validate it. Accepts VAST 2.0-4.4, VMAP 1.0, and DAAST 1.0/1.1 (auto-detected). Handles redirects. Use max_depth to control how deep VAST wrapper chains are followed (default 5, per IAB VAST 4.x recommendation). AI agents typically receive VAST URLs rather than raw XML — use this tool for that case. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: validate raw XML vs. validate fetched URL vs. inspect wrapper chain vs. fix vs. rule listing/detail vs. capability discovery. Even the two URL-fetching tools differ in intent—one validates, the other provides structured creative analysis—and their names make the distinction clear.
All tools follow a consistent verb_noun snake_case pattern: inspect_vast, explain_rule, fix_vast, get_adcp_capabilities, list_rules, validate_vast, validate_vast_url. The verbs are precise and the objects are consistently named, creating a predictable and intuitive surface.
Seven tools is well-scoped for a VAST validation and fixing server. Each tool fills a necessary role: validation (raw and URL), inspection, fixing, rule reference, rule detail, and protocol capability discovery, with no redundancy or bloat.
The tool surface covers the full validation workflow: validate input, understand issues, look up rules, fix issues, and re-validate, plus deep inspection of wrapper chains for debugging. Supporting VMAP/DAAST and including AdCP capabilities discovery rounds out the domain without obvious dead ends.