Skip to main content
Glama

Funcheap

by io.github.pipeworx-io

Search Events

search_events
Read-onlyIdempotent

Search SF Bay Area free & cheap events/deals from Funcheap. Filter by keyword, facet tags (e.g. "free", "live-music", "comedy", "art", "family-friendly", "food"), and a published-date window. Returns newest first by default. Use the tags/categories tools to discover facet slugs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1).
tagsNoComma-separated tag slugs to require, e.g. "free,live-music". Discover via the tags tool.
afterNoOnly posts published on/after this ISO date, e.g. "2026-06-19" or "2026-06-19T00:00:00".
queryNoFull-text keyword search, e.g. "outdoor movie" or "jazz".
beforeNoOnly posts published on/before this ISO date.
orderbyNoSort order (default "date" = newest first; "relevance" requires query).
per_pageNoResults per page (1-50, default 20).
categoriesNoComma-separated category slugs, e.g. "san-francisco,fairs-festivals".

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context about default sorting (newest first) and the scope (SF Bay Area), which enhances transparency. It does not contradict annotations.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. No redundant or vague phrases.

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 lack of output schema, the description could briefly mention return format (e.g., list of events), but the default sort order and available filters are well-documented. The tool is sufficiently contextual for selection.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the purpose of facet tags and directing users to the tags tool for slug discovery. It does not repeat schema details unnecessarily.

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 identifies the tool as searching SF Bay Area free/cheap events from Funcheap, with specific filters like keyword, facet tags, and date range. It distinguishes itself from sibling tools (tags, categories) by referencing them for facet discovery.

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?

The description provides explicit guidance on using the tags/categories tools to discover facet slugs, and states default sort order (newest first). However, it does not mention when not to use this tool vs. alternatives, though the siblings are complementary rather than competing.

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

All Funcheap 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.1/5.0
Disambiguation4/5

Most tools are distinct (event search, subscriptions, memory, Polymarket arbitrage, data lookups), but ai_visibility_check, scan_competitor_ai_presence, bet_research, polymarket_edges, and polymarket_arbitrage have overlapping purposes around competitive research and prediction-market edge-finding. The detailed descriptions disambiguate them, though an agent could confuse polymarket_edges with polymarket_arbitrage.

Naming Consistency4/5

Tool names are mostly descriptive and consistent: search_events, event, categories, tags are aligned; ask_pipeworx, compare_entities, entity_profile follow a similar pattern. However, polymarket_* tools have an odd mix of `polymarket_arbitrage`, `polymarket_fill_risk`, and `polymarket_edge_tracker`, and discover_tools/recent_alerts/recent_changes are consistent, mostly. Naming is quite consistent overall with minor deviations.

Tool Count3/5

At 35 tools, the count is heavier than typical MCP servers, but it reflects a broad service (Funcheap data + Pipeworx data platform + pred markets). Still, plenty of tools serve the same primary purpose (polymarket_, ask_pipeworx variants) so some pruning would improve the surface.

Completeness4/5

The surface appears complete for its domain: search/retrieve events, category/tag navigation, memory, subscriptions (create/list/cancel/pull), data lookups, entity resolution, comparisons, profiles, edge scanning, and feedback. Minor gaps include no direct 'update' on events (but events are static), and no pricing fetch tool separate from event text, though body text covers it.

Resources