Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Web app manifest audit

web-technology_web-manifest-audit
Read-onlyIdempotent

Validate a web app manifest against W3C installability checks for start_url, scope, display and icons. Price $0.02 USDC. POST /api/v1/web-technology/web-manifest-audit. 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": {
      "manifest": "<manifest>",
      "manifestUrl": "<manifestUrl>",
      "documentUrl": "<documentUrl>"
    },
    "name": "web-technology_web-manifest-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYesmanifest, object. Required.
documentUrlYesdocumentUrl, string, uri. Required.
manifestUrlYesmanifestUrl, string, uri. Required.

Output Schema

NameRequiredDescriptionDefault
errorsNoerrors. Array.
sourcesNosources. Array.
resolvedNoresolved. Object.
warningsNowarnings. Array.
limitationsNolimitations. Array.
installabilityHintsNoinstallabilityHints. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the supplied annotations, the description discloses important behavior: the price ($0.02 USDC), the endpoint (POST /api/v1/web-technology/web-manifest-audit), and what happens on an unpaid call (returns x402 payment terms and does not run). This is significant operational context that the annotations alone do not provide.

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?

The description is three tightly written sentences with the purpose front-loaded followed by payment and unpaid-call behavior. Every sentence earns its place by adding operational or scope information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex with a nested manifest object and an output schema. The description covers purpose, validations, pricing, endpoint, and unpaid-call behavior, leaving nothing critical unknown for an agent to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents all three parameters. The description mentions manifest fields being checked but does not add meaning about the manifest, manifestUrl, or documentUrl parameters beyond what the schema provides.

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 states a specific verb and resource: validate a web app manifest against W3C installability checks. It names the exact checks (start_url, scope, display, icons), making the tool's scope unambiguous and distinguishable from sibling validators like ads-txt or security-txt.

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?

The description gives clear context for using the tool: auditing a manifest for installability. It does not explicitly state when to avoid it or list alternative tools, but the purpose is narrow enough that the intended use is obvious.

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