Skip to main content
Glama

Disney

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/5.0
Behavior1/5

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

The description contradicts annotations: it states mark_read:true flags events read (a write operation), while annotations declare readOnlyHint=true (implying no state changes). This contradiction undermines trust in the tool's behavior.

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?

The description is brief yet comprehensive, front-loaded with the primary action. Each sentence adds value—covering parameters, alternative access, and polling advice—without redundancy.

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 lacking an output schema, the description fully outlines return fields (source, citation_uri, payload), all parameter behaviors, and usage context (e.g., polling, alternative feed). It is self-sufficient for understanding the tool.

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?

Schema coverage is 100%, and the description adds rich semantics: it explains filter examples (e.g., 'sec_8k'), mark_read semantics, default limit (50), and since meaning, going well beyond the schema's raw descriptions.

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 'Pull fired events from your subscription feed' with a specific verb and resource. It details what each returned event carries (source, citation_uri, raw payload), differentiating it from sibling tools like subscribe or list_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?

The description advises filtering by type and since, explains polling suitability, and notes an alternative API endpoint. It lacks explicit exclusion of sibling tools but provides sufficient context for when to use this tool.

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

All Disney 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.6/5.0
Disambiguation5/5

Each tool has a highly distinct purpose, from Disney character lookups to financial data and prediction market analysis. Agent can easily distinguish them by name and description.

Naming Consistency2/5

Naming conventions vary wildly: some use verb_noun (list_characters), others are phrases (ask_pipeworx) or compound nouns (polymarket_arbitrage). No consistent pattern across tools.

Tool Count1/5

34 tools is far too many for a Disney-themed server. Only 3 tools (list_characters, search_characters, get_character) relate to Disney; the rest are general-purpose data tools that belong elsewhere.

Completeness1/5

For a Disney server, the tool surface is severely incomplete. Missing basic CRUD for characters, no info on movies, parks, or media. Extraneous tools do not fill these gaps.

Resources