Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PUBDATA_MCP_MAX_SPEND_USDCNoThe lifetime spend cap in USDC for the paid tool (default 0.10 USDC total across the life of the state file). Delete the state file to reset.0.10

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
base_feeA

Current Base L2 gas fee estimate (gwei), for costing x402 payments before making them.

earthquakesA

Recent earthquakes worldwide (USGS), magnitude-ordered, with place, time and coordinates.

issA

Current position and altitude of the International Space Station.

weatherA

Live weather for a coordinate: temperature, wind, and a condition word.

postcardA

A few lines of live verse composed from the weather, the nearest recent earthquake and the ISS position at a coordinate. Human-legible; nice for demos.

spend_statusA

Show this MCP server's local x402 spend cap: cap, amount authorised so far, and remaining. Use it to decide before calling a paid tool.

risk_briefA

PAID (x402, USDC on Base): a single fused brief for a coordinate — weather, nearest seismic activity and an exposure summary. Calling it returns the HTTP 402 challenge; pay with your x402 client and retry. This MCP server never touches your wallet.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation4/5

Most tools map to a distinct data source (base_fee, iss, earthquakes, weather) or payment concern (spend_status). The only mild overlap is between postcard and risk_brief, which both fuse weather + seismic + ISS/coordinate data; descriptions differentiate them (free novelty verse vs. paid exposure brief), but an agent could still hesitate between the two fusion tools.

Naming Consistency4/5

All names are lowercase snake_case (base_fee, spend_status, risk_brief) with no camelCase mixing, which is predictable. However, they are noun/endpoint style rather than a clear verb_noun convention, and the bare acronym 'iss' breaks the compound-word pattern slightly.

Tool Count5/5

Seven tools is well-scoped for a read-only public-data server: four raw data sources, one composite demo tool, one paid fused brief, and one payment-cap status check. Each tool has a clear reason to exist and nothing feels padded.

Completeness4/5

For a read-only data domain the surface is solid: raw feeds, a fusion tool, and x402 payment-costing/status tools. Minor gap is the lack of any spend-cap management or authorization operation (spend_status is read-only), and no batch/coordinate-list variant, but core workflows are coverable.

Maintenance

ActivityMaintained
ResponsivenessNo issues