Skip to main content
Glama

webbersites-x402-data-api

by io.github.webberdesign

post_brand_kit

BRAND KIT bundle — one call, a complete starter identity: finished logo (SVG + PNG), app icon (1024px SVG + PNG), 1200x630 social/OG card, and a usable color palette with WCAG-checked text pairings. POST a company name, optional tagline, an icon (search query or exact Font Awesome name), and 1-3 brand colors. Everything matches: same mark, same colors, same fonts. The pieces individually total ~$0.05; the kit is $0.05 and adds the palette and coherence. ($0.05 per call, paid via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fontNomontserrat, playfair, space-grotesk, bebas, poppins, dm-serif — omit for random
iconNoExact Font Awesome icon name (skips search)
nameYesCompany/product name (required, max 40 chars)
queryNoIcon search text — best Font Awesome match becomes the mark
shapeNoMark shape: squircle (default), rounded, circle, square
themeNoSocial card theme: dark (default), light, midnight
colorsNo1-3 brand colors, hex or CSS names
domainNoDomain shown on the social card
layoutNoLogo layout: bottom (default), top, left, right
taglineNoOptional tagline (max 60 chars)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNo
logoNo
nameNo
og_cardNo
paletteNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations are minimal (only readOnlyHint, openWorldHint, etc.) and the description adds pricing information ($0.05 per call) and the nature of the output (kit with coherence). No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single paragraph that front-loads purpose and then lists inputs. It is informative but could be more structured with bullet points for 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?

Covers what the tool does, inputs, outputs (logo, icon, social card, palette), and cost. With an existing output schema, return format details are not needed. Lacks error cases but overall complete.

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% but description adds extra constraints like character limits for name and tagline, and explains how icon can be a query or exact name. Provides orientation beyond schema.

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 clearly states the tool creates a complete brand kit bundle including logo, app icon, social card, and color palette. It distinguishes from sibling tools like post_logo_generate by emphasizing the bundle's coherence and cost advantage.

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 for a complete starter identity and compares to individual pieces, but lacks explicit when-to-use or when-not-to-use guidance relative to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All webbersites-x402-data-api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but the SEO-related tools (head_check, full_audit, site_audit, etc.) overlap in scope, potentially causing confusion despite clear descriptions.

Naming Consistency5/5

Tool names consistently follow a get_/post_/delete_ verb pattern with descriptive noun phrases (e.g., get_seo_head_check, post_store_collection), with no mixing of naming conventions.

Tool Count2/5

With 46 tools covering a wide breadth of domains (SEO, accessibility, music, crypto, linting, etc.), the count is excessive for a single server, feeling unfocused and heavy.

Completeness4/5

The tool set covers most core operations for each sub-domain, but minor gaps exist (e.g., missing update for datastore, limited music operations).

Resources