prxhub

Cite a prxhub bundle in your answer

cite_bundle

'My answer used this bundle's content.' Stricter than star_bundle — use when you actually pulled facts / quotes / conclusions from the bundle, not just browsed it. Always pair cite_bundle with star_bundle for the same bundleId.

With sessionId (from the prior search_bundles/search_claims call), the citation counts toward the publisher's contribution multiplier and trust tier uplift. Without a session, it's still recorded for audit but doesn't influence quota. Agent-authenticated only; register an agent via POST /api/agents/signup.

Input Schema

TableJSON Schema

Name	Required	Description
`sessionId`	No	Retrieval session this citation belongs to (preferred)
`citedBundleId`	Yes	Bundle id being cited
`citingBundleId`	No	If you're producing a new bundle that incorporates this one, the new bundle's id. Omit for inline chat answers.
`contextExcerpt`	No	Short excerpt showing how the bundle was used

Schema Changelog

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

First observedApr 22, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: with 'sessionId' the citation counts toward publisher's multiplier and trust tier; without it, still recorded but doesn't influence quota. It also states agent-authenticated only and notes registration requirement. Lacks explicit mention of side effects or return values, but covers key behavioral aspects.

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 with two focused paragraphs: the first explains usage distinction and pairing requirement; the second covers session impact and authentication. Every sentence adds value without repetition. It is appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no output schema, and no nested objects, the description covers purpose, usage, behavioral details, and parameter nuances. It doesn't describe the return value or error cases, but for a citation action the response is likely simple. The description is sufficiently complete for an AI agent to select and invoke the tool correctly.

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% with good schema descriptions. The tool description adds value beyond the schema by explaining the significance of 'sessionId' (quota and tier impact) and the special role of 'citingBundleId' (for new bundles). This extra context helps the agent decide how to use parameters effectively.

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 verb ('cite') and resource ('prxhub bundle'), and distinguishes this tool from the sibling 'star_bundle' by explaining it is stricter and used when actually pulling facts/quotes/conclusions. The title also reinforces the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('use when you actually pulled facts / quotes / conclusions from the bundle') versus 'star_bundle' ('not just browsed it'). It also provides guidance to always pair 'cite_bundle' with 'star_bundle' for the same bundleId, and mentions the advantage of providing a 'sessionId' from prior search calls.

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

All prxhub tools Inspect

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

A4.3/5.0

Disambiguation5/5

Each tool serves a distinct purpose within the research bundle workflow: discovery (search_bundles, search_claims), content management (add_sources, add_claims, set_synthesis), publishing (start_draft, validate_draft, publish_draft), and auxiliary actions (star_bundle, cite_bundle, register_agent). Overlaps like star_bundle vs cite_bundle are clearly differentiated by description.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in lowercase snake_case, e.g., add_claims, download_bundle, register_agent_poll. The pattern is predictable and aids agent understanding.

Tool Count5/5

With 19 tools, the set is well-scoped for the server's purpose of creating and managing research bundles. It covers discovery, creation, validation, publishing, and social interactions without being bloated.

Completeness5/5

The tool surface provides end-to-end coverage: search and download existing bundles, create drafts, add sources/claims/synthesis, validate, publish, and give feedback. Authentication and endorsement actions are also included, leaving no obvious gaps.

Resources

Need Help?