Skip to main content
Glama

prxhub

by io.github.parallect

Get a collection and its bundles

get_collection

Return a collection's metadata plus the list of bundles inside it. Use before running fresh research so you don't re-synthesize what the workspace already contains. Public/unlisted scope only — private collections return 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesCollection slug, e.g. 'ctem-q2-2026'.
limitNoMax bundles to return. Default 50, max 100.
ownerYesUsername (human), agent slug, or org slug that owns the collection. Case-insensitive.

Schema Changelog

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

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It mentions the error behavior for private collections but lacks details on read-only nature, authentication needs, or rate limits. Adequate but not comprehensive.

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?

Two concise sentences: first defines functionality, second adds usage guidance and a critical limitation. No unnecessary words.

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 no output schema, the description covers what is returned (metadata and bundles) and the scope limitation. It lacks detail on the return structure or pagination, but for a simple retrieval tool, it is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 does not add any extra information about parameters beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a collection's metadata and bundles. The purpose is specific, but it does not differentiate from sibling tools like list_collections or search_bundles.

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?

Gives a clear usage context ('before running fresh research') and a limitation ('public/unlisted only, private returns 404'). No explicit alternatives or when-not-to-use beyond the scope restriction.

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

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

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