Skip to main content
Glama

Podcastindex

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.6/5.0
Behavior5/5

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

Discloses key behavioral traits: key-value storage scoped by identifier, persistence differences between authenticated and anonymous sessions (24 hours). This adds value beyond annotations, which only indicate idempotence.

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?

Five sentences efficiently cover purpose, usage, technical details, and tool relationships. No extraneous content.

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?

Missing no critical information for a simple key-value store. No output schema needed as behavior is clear. Could mention error conditions or size limits, but overall 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?

The input schema has 100% description coverage with examples. The tool description repeats these examples without adding new parameter-level detail, so baseline 3 applies.

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 saves data for later reuse, with specific examples (tickers, addresses, preferences). It distinguishes from sibling tools by explicitly mentioning recall and forget.

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 on when to use: when discovering something worth carrying forward. It also advises pairing with recall and forget, offering clear context for alternatives.

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

All Podcastindex 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.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but ask_pipeworx and ask_pipeworx_grounded overlap (one is grounded), and bet_research/validate_claim/compare_entities/entity_profile all query Pipeworx data with different intents, which could cause confusion.

Naming Consistency4/5

Names are consistently lower_snake_case and mostly follow a verb_noun pattern (e.g., search_podcasts, get_podcast, list_subscriptions). A few compound names like pipeworx_feedback and polymarket_arbitrage deviate slightly but remain readable.

Tool Count2/5

30 tools is excessive for a server named 'Podcastindex'. It aggregates unrelated domains (podcasts, Pipeworx queries, Polymarket, memory, etc.), making it feel like a kitchen sink rather than a focused tool set.

Completeness3/5

For podcasts, the tool set covers search, metadata, episodes, and trending but lacks subscription management. For the broader Pipeworx domain, ask_pipeworx and discover_tools provide wide access, but specific gaps exist (e.g., no direct SEC filing query). Overall, the surface is broad but uneven.

Resources