Skip to main content
Glama

Jsonplaceholder

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

A3.9/5.0
Behavior1/5

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

The description contradicts the annotation readOnlyHint:true by revealing that setting mark_read:true flags events as read, which is a state-changing side effect. Despite adding useful details like payload structure, this annotation contradiction forces a score of 1 per the rules.

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 concise, front-loaded with the core purpose, and every sentence provides useful information—filtering, return fields, mark_read behavior, and an alternative access method. No fluff or repetition.

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 covers return payload details, filtering options, side effects, and polling suitability. It gives a complete picture for an agent to invoke the tool correctly, aside from the annotation contradiction which is a separate issue.

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% for all 5 parameters, giving a baseline of 3. The description adds value by giving a concrete example of type (“sec_8k”), clarifying since as an ISO timestamp, and explaining the mark_read side effect on subsequent calls, which goes beyond the schema 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 the tool's purpose: 'Pull fired events from your subscription feed' and specifies it returns recent alerts with source, citation_uri, and raw payload. This distinguishes it from sibling tools like get_posts or list_subscriptions by focusing on fired events from the subscription feed.

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 provides clear usage context: it mentions filtering by type and since, explains the mark_read behavior, and states that polling works fine, even offering an alternative HTTP endpoint for scripts/dashboards. It does not explicitly exclude other tools but gives enough context for typical use.

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

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

Multiple tools overlap heavily: ask_pipeworx_beta is explicitly identical to ask_pipeworx, and ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim all serve natural-language question answering. The JSONPlaceholder get_* tools are distinct but introduce an unrelated domain, making tool selection ambiguous in practice.

Naming Consistency3/5

All names use lowercase snake_case, which is a consistent style, but there's no uniform verb_noun pattern. Tools mix action-first names (get_posts, remember, resolve_entity) with noun-oriented names (entity_profile, deep_research, pipeworx_trending). The naming is readable but not highly predictable.

Tool Count2/5

35 tools is far beyond the typical well-scoped range of 3-15. The set includes a full suite of Pipeworx/Polymarket tools plus a separate JSONPlaceholder demo namespace, making the server feel bloated and unfocused. Many meta-tools (discover_tools, suggest_questions, pipeworx_trending) could be consolidated.

Completeness2/5

The server's name and the get_posts/get_post/get_comments/get_users tools suggest a JSONPlaceholder fake API, but CRUD operations are missing: there's no create, update, or delete for posts, comments, or users, and no todos, albums, or photos. The unrelated Pipeworx/Polymarket tools don't address this core domain gap.

Resources