Skip to main content
Glama

Httpstatus

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

A3.8/5.0
Behavior1/5

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

Annotation contradiction: tool is marked readOnlyHint=true yet the description details a side effect (mark_read:true flags events as read, modifying state). This contradicts the read-only hint.

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?

Four sentences cover purpose, return fields, filtering, side effect, and alternative access, with no unnecessary detail. Information is front-loaded.

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?

Given no output schema and optional params, the description covers key return fields, filtering, and side effect. Lacks explicit mention of default ordering or edge cases, but overall adequate.

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%, and the description adds meaningful value beyond the schema by explaining the mark_read effect and the feed context, enhancing parameter understanding.

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', distinguishing it from sibling tools that may involve searching or other actions.

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?

It mentions that polling works and provides an alternative endpoint for scripts/dashboards, but does not explicitly compare to siblings like 'search_within' or state when not to use.

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

All Httpstatus 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
Disambiguation4/5

Most tools have distinct purposes, but ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very similar, causing potential confusion. The memory tools (remember/recall/forget) are separate, but the overall set is diverse enough that agents can typically distinguish them.

Naming Consistency2/5

Tool names use a mix of camelCase (ask_pipeworx, entity_profile, generate_llms_txt) and snake_case (http_status, list_http_statuses, list_subscriptions), with no consistent verb_noun pattern. Some names are descriptive, but the lack of a unified convention hurts predictability.

Tool Count2/5

33 tools is high for a server named 'Httpstatus' that only has two HTTP-related tools. The large number spans data retrieval, memory, subscriptions, prediction markets, and more, making the server feel bloated and unfocused.

Completeness3/5

The server covers many domains but each is incomplete. HTTP status has lookup and list but no lifecycle. Memory tools are basic. Data retrieval is extensive but not exhaustive for any single domain. It's a broad but shallow collection.

Resources