Skip to main content
Glama

bidclub

by ai.bidclub
OverviewDiscussionsAdmin

Feed index

bidclub_feed_index

The slim catalogue of every episode — one row each, metadata only. Narrow it with show or person; passing both is an error. Large responses are truncated to the newest rows with a note, so filter rather than paging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showNoShow id. Mutually exclusive with person.
assetNoOptional asset tag ids joined by commas (equities, crypto, vc_pe, other). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.
focusNoOptional focus tag ids joined by commas (investing, company_building, technical, macro, policy). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.
personNoExact participant name. Mutually exclusive with show.
sectorNoOptional sector tag ids joined by commas (ai_software, semis, robotics, biotech, consumer, finance, blockchain, energy, space_defense). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / asset
      Added value: +{
+  "description": "Optional asset tag ids joined by commas (equities, crypto, vc_pe, other). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.",
+  "pattern": "^(?:none|(?:equities|crypto|vc_pe|other)(?:,(?:equities|crypto|vc_pe|other))*)$",
+  "type": "string"
+}
    • addedInput schema / properties / focus
      Added value: +{
+  "description": "Optional focus tag ids joined by commas (investing, company_building, technical, macro, policy). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.",
+  "pattern": "^(?:none|(?:investing|company_building|technical|macro|policy)(?:,(?:investing|company_building|technical|macro|policy))*)$",
+  "type": "string"
+}
    • addedInput schema / properties / sector
      Added value: +{
+  "description": "Optional sector tag ids joined by commas (ai_software, semis, robotics, biotech, consumer, finance, blockchain, energy, space_defense). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.",
+  "pattern": "^(?:none|(?:ai_software|semis|robotics|biotech|consumer|finance|blockchain|energy|space_defense)(?:,(?:ai_software|semis|robotics|biotech|consumer|finance|blockchain|energy|space_defense))*)$",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behavioral traits: output shape ('one row each, metadata only'), an error condition ('passing both is an error'), and truncation of large responses to newest rows with a note. It stops short of stating read-only safety or auth requirements, but covers the main operational behaviors an agent needs.

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 sentences, front-loaded with the core purpose, then usage constraints and truncation behavior. Every sentence earns its place with zero filler or redundancy.

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 absence of an output schema and annotations, the description adequately explains the result format (rows, metadata only) and the truncation caveat. It might specify the metadata fields or note contents, but it is sufficient for an agent to understand and invoke the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds the mutual exclusivity of show/person and the 'filter rather than page' tip, but these are already present or implied in the schema descriptions. It does not meaningfully enhance understanding of individual parameters beyond the schema.

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?

Description states a clear verb+resource: a 'slim catalogue of every episode — one row each, metadata only.' It distinguishes itself through 'slim' and 'metadata only' from likely sibling tools like get_episode or search_episodes, but does not explicitly name alternatives, so it misses the full sibling differentiation that would merit a 5.

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 concrete usage context: how to narrow by show or person, that passing both is an error, and the truncation behavior advising to filter rather than page. This offers clear context for calling the tool, though it does not explicitly route the agent to/away from sibling tools.

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

All bidclub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources