Skip to main content
Glama
Sign In

ZERO Payment Guard

by host.beacon.worker.zero-payment-guard
OverviewDiscussionsAdmin

Company brief (enrichment + homepage/About Markdown) ($0.003 USDC on Base via x402)

company_brief
Read-onlyIdempotent

Paid $0.003 per call (x402, USDC on Base). One call to research a company: everything domain_enrich returns (socials, email provider, SPF/DMARC, DNS provider, RDAP age, tech stack, SaaS signals) plus its homepage and About page as clean Markdown.

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": {
      "domain": "<domain>"
    },
    "name": "company_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, URL or work email
maxCharsNoMax Markdown chars per page, default 6000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior. The description adds important context beyond them: the $0.003 per-call cost, x402/USDC-on-Base payment rail, and a clear list of returned data including homepage and About Markdown.

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?

Two sentences, no filler. The payment model is front-loaded and the second sentence packs the returned data categories efficiently.

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 two-parameter read-only enrichment tool with no output schema, the description is largely complete: it lists the enrichment fields and confirms homepage/About Markdown output. Minor gaps remain around output shape and behavior when an About page is absent, but these are not severe.

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 domain and maxChars parameters are already documented in the schema. The description adds no parameter-specific semantics beyond what the schema provides, making the baseline 3 appropriate.

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: "One call to research a company." It distinguishes the tool from domain_enrich by explicitly saying it returns everything domain_enrich returns plus homepage and About page Markdown.

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 when to use it: when you want domain enrichment plus page content in one paid call. However, it does not explicitly say when to prefer this over domain_enrich or page_extract, nor does it state exclusions or alternatives.

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

All ZERO Payment Guard toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources