Skip to main content
Glama

crossref

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent. The description adds meaningful context: self-aggregating signal, derived from CF analytics-engine, no PII, and caching behavior (5min-1h depending on window). This goes beyond annotations and gives the agent useful expectations about data freshness and privacy.

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 with a strong lead, a concise output summary, bulleted use cases, and a compact caveat set. Every sentence earns its place; no fluff or repeated schema information.

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?

For a read-only tool with one optional parameter and no output schema, the description covers purpose, outputs, use cases, privacy, and caching. It is fully adequate for an agent to understand when and how to invoke it.

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 window parameter has a clear enum and default. The description adds interpretive value by explaining the trade-off between shorter and longer windows, which is not present in the schema's enum definition.

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 opens with a clear, specific purpose ('What other AI agents are calling on Pipeworx right now') and lists exact outputs ('top tools, top packs, and total call volume'). It clearly distinguishes itself from sibling tools like ask_pipeworx or discover_tools by focusing on aggregated trending signal.

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 three explicit use cases (discovering hot data sources, confirming canonical tools, aligning with agent needs) and explains how window choice affects results ('shorter windows surface what's hot right now; longer windows show steady-state demand'). It doesn't name specific alternatives for exclusion, but gives clear guidance on when to use it.

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

All crossref 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.8/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve queries, with ask_pipeworx_beta explicitly identical to ask_pipeworx. Prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, bet_research, etc.) also have unclear boundaries, making tool selection tricky for an agent.

Naming Consistency4/5

Tool names are consistently lowercase snake_case with a mostly verb-first pattern (get_work, search_works, list_subscriptions, validate_claim). Minor deviations exist: some names are noun-first (entity_profile, recent_changes) and prefixes vary (get/search/list/ask/scan), but the overall convention is predictable and readable.

Tool Count2/5

34 tools is far too many for a server named 'crossref', and only three tools actually relate to Crossref. The rest form a sprawling utility belt covering data routing, memory, subscriptions, prediction markets, AI visibility, and npm scanning — a scope mismatch that makes the server feel like a kitchen sink rather than a focused offering.

Completeness2/5

The Crossref-specific surface is thin: search_works, get_work, and get_journal cover discovery and metadata but lack citation lookup, author search, and funder information. The broader Pipeworx surface is extensive but has no unifying domain, so it's impossible to consider the overall toolset complete for any coherent purpose.

Resources