Skip to main content
Glama

Jpl Ssd

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.3/5.0
Behavior4/5

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

Beyond annotations (readOnly, idempotent, non-destructive), description discloses that setting mark_read:true will flag events as read to affect subsequent calls. This adds behavioral context not captured in annotations, enhancing transparency.

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, front-loaded with the main action. Each sentence adds distinct value: what it does, what it returns, filter options, mark_read effect, and alternative access. No unnecessary words.

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?

Despite no output schema, description specifies return fields (source, citation_uri, raw payload) and flags mark_read behavior. Covers filtering, limits, and alternative access, making it complete for a read-only tool with five optional parameters.

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 coverage is 100%, so parameters are well-documented. Description adds examples (e.g., 'sec_8k', 'ISO timestamp') and reinforces the mark_read behavior, meeting the baseline for high coverage but not exceeding significantly.

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?

Description clearly states 'Pull fired events from your subscription feed' with specific verb and resource. It details what is returned (source, citation_uri, payload) and distinguishes from siblings like list_subscriptions by focusing on reading alerts rather than managing subscriptions.

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 practical guidance: mentions filtering by type and since, suggests polling works, and notes an alternative HTTP endpoint for scripts/dashboards. While it doesn't explicitly exclude scenarios, the context is sufficient for appropriate use.

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

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

Multiple tools overlap in purpose, especially the ask_pipeworx variants and the polymarket_* tools. An agent would struggle to distinguish between similar functions, increasing the risk of selecting the wrong tool.

Naming Consistency2/5

Tool names use inconsistent conventions: some are snake_case (close_approaches), some are verb_noun (generate_llms_txt), and others mix styles (ask_pipeworx vs. deep_research). No clear pattern is maintained across the set.

Tool Count1/5

At 35 tools, the server is bloated and unfocused. The majority of tools are unrelated to the 'Jpl Ssd' domain, which only has 4 relevant tools. The count is far too high for the stated purpose.

Completeness2/5

The JPL SSD coverage is minimal (only 4 tools), missing key functionalities like detailed object queries or bulk downloads. The remaining tools cover unrelated domains, so the surface is both incomplete for its primary domain and cluttered with off-topic tools.

Resources