Skip to main content
Glama

prxhub

by io.github.parallect

Send feedback about a search session

session_feedback

Voluntary feedback channel. Call ONLY when the user explicitly asks to give feedback, or when retrieval was confusing / wrong / incomplete in a way worth reporting. Smooth runs should NOT call this — no news is good news.

Pass sessionId from the prior search plus any combination of bundles[], claims[], sources[] with useful/agree/quality flags and a short reason in the user's own words (not your summary). Empty arrays are legal — calling with sessionId and nothing else acks 'this search returned nothing useful' without further detail. Agent-authenticated only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimsNo
bundlesNo
sourcesNo
sessionIdYesSession id returned by search_bundles/search_claims

Schema Changelog

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

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: it is an agent-authenticated write operation, legal with empty arrays, and expects user's own words (not AI summary). No contradictions.

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?

Description is 4 sentences, all densely informative with zero waste. Front-loads the core rule ('Voluntary feedback channel'), then expands with usage constraints and parameter notes. Every sentence earns its place.

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 no output schema and moderate parameter complexity, the description gives complete context: when to use, what each parameter represents (with flags), authentication requirement, and special behavior for empty arrays. No gaps remain.

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 25% (only sessionId described). The description compensates by explaining the purpose of bundles[], claims[], sources[] and their flags (useful/agree/quality), plus the reason field requirement ('in the user's own words'). This adds critical meaning beyond the schema.

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 explicitly states 'Voluntary feedback channel' and defines its purpose: sending feedback about a search session. It clearly distinguishes from siblings by focusing on user-requested feedback or error reporting, not on search or collection operations.

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?

Provides explicit guidance: 'Call ONLY when the user explicitly asks to give feedback, or when retrieval was confusing/wrong/incomplete in a way worth reporting.' Also states when not to call ('Smooth runs should NOT call this') and offers a fallback behavior (empty arrays ack 'nothing useful').

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