Skip to main content
Glama

Spoonacular

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).

TDQS

A4.7/5.0
Behavior5/5

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

Despite readOnlyHint=true, the description transparently discloses that setting mark_read:true mutates read state, and notes that polling is safe. It also reveals the persisted feed nature and the payload structure, adding substantial context beyond the annotations.

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?

Three sentences, front-loaded with the main purpose, and every sentence earns its place—covering return value, filtering, side effects, and external access. No fluff.

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?

With no output schema, the description covers the return format (source, citation_uri, raw payload), filtering, side effects, and polling behavior. It is thorough for a read-oriented tool with 5 optional params.

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%, so baseline is 3. The description enriches key parameters with examples ('sec_8k'), clarifies 'since' semantics, and explains the side effect of mark_read. It does not mention limit or unread_only explicitly, but those are well-described in the schema.

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 uses a specific verb ('Pull') and resource ('fired events from your subscription feed'), clearly distinguishing this tool from siblings like recent_changes or list_subscriptions. It also specifies what each alert carries (source, citation_uri, raw payload).

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 clear context on when to use (fetching recent alerts from a feed) and how to filter, along with an explicit alternative HTTP endpoint for scripts/dashboards. However, it does not explicitly mention alternative tools or when not to use the tool, so it's not a 5.

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

All Spoonacular 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

B3/5.0
Disambiguation2/5

The tool set bundles three unrelated domains, and within them several tools are near-indistinguishable: ask_pipeworx_beta is explicitly identical to ask_pipeworx, ask_pipeworx_grounded overlaps with validate_claim, bet_research/polymarket_edges/polymarket_arbitrage all target betting opportunities, and meal_plan_generate duplicates meal_plan_week. The aspect-specific recipe fetchers (ingredients/nutrition/summary/taste) also blur with recipe_information.

Naming Consistency3/5

Most tools follow a reasonable snake_case verb_noun pattern (recipe_search, resolve_entity, compare_entities, unsubscribe), and each cluster (recipe_*, polymarket_*, ask_pipeworx*) is internally consistent. However, conventions fragment across clusters — bare verb memory tools (remember, forget, recall), the ask_pipeworx_beta/_grounded suffix family, and the odd generate_llms_txt — so no single predictable scheme governs the whole surface.

Tool Count2/5

49 tools is far too many for a coherent surface, and crucially the count is misaligned with the server's stated identity: only 18 of 49 tools actually belong to the Spoonacular food domain, while 27 are Pipeworx data/prediction-market tools and 3 are generic memory utilities. The server appears to be three products mashed into one.

Completeness3/5

For the core Spoonacular food domain the surface is reasonably complete — search for recipes/products/ingredients, detail fetchers, meal plans, wine pairing, and unit conversion all exist. But the overwhelming presence of unrelated Pipeworx and memory tools makes the server's actual purpose ambiguous, and gaps are hard to assess when the food tools share the namespace with SEC filings and Polymarket arbitrage.

Resources