Skip to main content
Glama

Easypost

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

Schema Changelog

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

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Discloses return fields (source, citation_uri, payload), filtering options, and the mark_read behavior which affects subsequent calls. Annotations already indicate idempotent and read-only, and the description adds valuable behavioral context.

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?

Concise yet comprehensive paragraph. Front-loaded with purpose, no wasted words. Every sentence adds value.

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?

Covers all parameters, explains return fields, gives polling advice, and mentions an alternative endpoint. No gaps given the tool's complexity and available annotations.

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

Parameters5/5

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

Adds meaning beyond the schema by giving examples (e.g., 'sec_8k' for type), explaining mark_read's effect, and clarifying limit range. Schema coverage is 100% but description enhances usability.

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 verb 'Pull' and the resource 'fired events from your subscription feed', explaining what it returns. It distinguishes from sibling tools like list_subscriptions by focusing on events/alerts.

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?

Provides guidance on polling and alternative access via URL. However, it does not explicitly contrast with sibling tools for when to use this versus others.

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

All Easypost 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.7/5.0
Disambiguation2/5

The ask_pipeworx family (stable, beta, grounded) are nearly identical, with beta explicitly matching stable, creating clear misselection risk. The five polymarket_* tools and several research tools (deep_research, bet_research, entity_profile) also overlap in purpose despite detailed descriptions.

Naming Consistency3/5

Tool names are mostly snake_case and readable, with consistent prefixes (ask_pipeworx_, polymarket_, easypost_), but mix verb-first (validate_claim, resolve_entity) and noun-first (entity_profile, ai_visibility_check) conventions. The server name 'Easypost' does not align with the overwhelmingly Pipeworx-focused tool set.

Tool Count2/5

33 tools is a heavy count, especially with three near-duplicate ask_pipeworx variants and many meta-tools. The set is also unfocused: only two shipping tools under an 'Easypost' label while the rest are a broad data-research and prediction-market platform, making the count feel bloated for the apparent scope.

Completeness2/5

As an Easypost server, shipping coverage is severely incomplete (rates and tracking only, no label purchase, address verification, or refunds). Within the Pipeworx tools, the cited pipeworx:// URIs have no direct fetch-by-URI tool, leaving a notable dead end for agents trying to retrieve full records.

Resources