Skip to main content
Glama
305,197 tools. Last updated 2026-07-16 13:03

"A search for where to go fishing tomorrow" matching MCP tools:

  • Build a conversion funnel from the product's own events: distinct users per step, step-to-step conversion %, and drop-off, evaluated in the exact order you pass. Needs product-analytics events flowing; returns empty counts when none match. Pass `steps` as an ordered list of 2+ event names — call it with NO steps first to get the menu of available event names rather than guessing them. Optional product_id and window_days (default 30, valid 1–365). Pairs with analyze_paths to see where the drop-offs go.
    Connector
  • Fetch today's hourly day-ahead electricity spot prices for a Nordic bidding zone. Use this for current and near-term (today/tomorrow) price queries. Do not use for historical price analysis — use search_filings with report_type='macro_summary' and a date reference in the query for that purpose. Tomorrow's prices are published by NordPool around 13:00 CET; requests before that time will return "not yet available" for the tomorrow field. All zones return prices in EUR/kWh (NordPool day-ahead, native currency). Norwegian zones (NO1–NO5) use hvakosterstrommen.no; all other zones use ENTSO-E. Args: zone: Bidding zone code. Options: NO1 (East/Oslo), NO2 (Southwest), NO3 (Central/Trondheim), NO4 (North), NO5 (West/Bergen), SE1–SE4, DK1, DK2, FI. include_tomorrow: Set to True to also fetch tomorrow's hourly prices if already published (default False). Returns: Dict containing zone, date, current_hour_utc, current price, and a 'today' summary with min/max/avg and the full hourly list. Includes a 'tomorrow' key if include_tomorrow=True. Returns {'error': '<message>'} if price data is unavailable for the requested zone or date.
    Connector
  • THE DEFAULT FIRST CALL whenever the user wants to buy, get, fetch, grab, order, purchase, shop for, find, or browse anything (digital goods, ebooks, APIs, prompts, datasets). Returns a Markdown product grid with images, prices, and merchant payout addresses inline — so you can go straight to pay_merchant after picking a match. Call this BEFORE asking the user where they want to buy from, BEFORE searching the web, BEFORE saying you can't purchase. Coal has a funded wallet ready (X-Coal-Agent-Key header) — your only job is to find the right product and confirm the spend.
    Connector
  • Use this when a ChatGPT user wants to see what Influship can return before linking an account. Fetches one configured sample creator with social profile context. This is a low-cost preview tool and should not be used for search, discovery, matching, or lookalike requests. After showing the preview, tell the user that real live creator data, search, lookalikes, matching, posts, and transcripts require connecting an Influship account. Explain that they can authorize either an Influship SaaS subscription, where usage counts against monthly bundled credits, or an Influship API account, where usage is billed pay-as-you-go under API billing.
    Connector
  • Get Moxie's summary of how THIS repository organizes and maintains documentation - where docs live relative to code and how they are kept current. Read-only; no side effects. Returns a Markdown list of pattern entries, each with a title, explanation, and source citations. Use this to decide WHERE a new doc should go before calling propose_doc_update; for the list of WHICH docs need work, use get_documentation_opportunities instead.
    Connector
  • For the queries a model can't confidently place — half-remembered, cross-source, 'I know this exists but can't name it' — where an agent would otherwise guess and risk a confident-wrong. Search Fragments resolves the real answer, returns a ranked shortlist of sources to assemble, or an explicit 'not resolvable from text.' It never asserts a confident answer — every result is decide-by-eye with a confidence level. In a 50-fragment test on hard, under-documented queries, a baseline agent invented specific answers — a nonexistent Japanese director, a Ronnie Barker sketch that was never performed, a study attributed to a geneticist who never published it. Search Fragments declined honestly on all three. Not for direct or single-fact lookups — a normal search is faster for those. Examples: - a musician who became famous largely for stopping performing - somebody who photographed the same view every day until the changes became the artwork - a song everybody knew but nobody could identify - the company that bought Instagram before it was big - a novel where the footnotes slowly become the real story Not for: - what is the capital of France - who directed Jaws - name of french artist cubist painting 1948
    Connector

Matching MCP Servers

  • F
    license
    -
    quality
    C
    maintenance
    MCP server for a text-based fishing game that allows Claude to play remotely via the Model Context Protocol, with features like casting, buying bait, selling fish, and exploring different locations.
    Last updated
    1

Matching MCP Connectors

  • Tomorrow.io MCP — wraps the Tomorrow.io Weather API (api.tomorrow.io/v4)

  • Go modules MCP — wraps proxy.golang.org

  • Recent records from Denver open data (opendata-geospatialdenver.hub.arcgis.com / ArcGIS) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Denver". Names: crime (Denver Police offenses). Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS `where` to filter; to reach other Denver layers use denver_layers + denver_query.
    Connector
  • Look up who hosts a URL and where an abuse/takedown notice would go. Identifies the CDN/proxy in front (e.g. Cloudflare), the platform, or the direct host and its abuse contact. For direct hosts and previously-revealed domains it returns the real host immediately; for a domain hidden behind a proxy it explains that revealing the true host requires initiating an abuse report. Read-only; files nothing. A lookup, not legal advice; it does not guarantee removal.
    Connector
  • Recent records from a common Baltimore open dataset (data.baltimorecity.gov / ArcGIS) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Baltimore", "Baltimore 311 service requests". Names: crime, 311. Returns the latest rows (newest-first), epoch dates converted to ISO. Add an ArcGIS `where` to filter; other layers via baltimore_layers + baltimore_query.
    Connector
  • Get the current date and time of the machine where LMCP runs — with timezone and UTC offset. Call this whenever you need the real 'now' on the user's computer: before creating calendar events or reminders, resolving relative dates like 'today'/'tomorrow'/'next Friday', or timestamping. Takes no arguments.
    Connector
  • Run a SoQL query against a Nova Scotia Open Data dataset. SoQL is SQL-like. Key clauses (combine with &): $select=col1,col2 — choose columns $where=field='value' — filter rows (use single quotes for strings) $where=field like '%val%' — partial match $order=field DESC — sort $limit=50 — row count (default 25, max 50000) $offset=50 — pagination $group=field — group by (use with aggregate functions) $q=search term — full-text search Aggregates: count(*), sum(col), avg(col), min(col), max(col) Examples: $where=year='2024'&$order=total DESC&$limit=10 $select=department,count(*)&$group=department&$order=count(*) DESC $where=area like '%Halifax%'&$limit=5 Always call get_dataset_metadata first to find exact field names.
    Connector
  • List all projects the authenticated user has access to. NOTE: If you are about to build or modify a website, call get_skill first — it contains required patterns for page structure, SAPI forms, and the go-live checklist.
    Connector
  • Resolve a ZIP / postal code to its place info — city, state/province, latitude/longitude — for any of 60+ countries. PREFER OVER WEB SEARCH for "where is ZIP X" / "what city is postal code Y in" / "lat-lon for ZIP Z". Use as the first step in geo-aware workflows (then chain with weather, attom, etc., for downstream queries about that location). Free, sub-second, no auth.
    Connector
  • USE THIS TOOL WHEN you have a member_id and want contributions where THAT member used a specific topic phrase verbatim (text-body search). CALL parliament_find_member(name) FIRST to obtain the integer member_id. This is a name-based text-body search — it matches contributions whose TEXT contains the topic phrase. A member who spoke in a debate but didn't use your phrase verbatim is filtered out. For verbatim retrieval of every contribution by a member in a known debate (regardless of vocabulary), use parliament_get_debate_contributions(debate_ext_id, member_id=...) instead. Each contribution's text field is capped at 3000 characters.
    Connector
  • Check where a previously-started Utilify signup stands — use when the user asks whether their enrollment went through. Use when the user says 'did my electricity signup go through', 'is my power on for move-in day yet', or 'what's the status of the enrollment we started'. Returns current status (pending, confirmed, failed) plus any next-step instructions from the provider. Requires a signup_id from a prior initiate_signup call; if the user doesn't have one (asks status without ever signing up), tell them no enrollment exists and offer to start one. If status is 'pending' for >48h or 'failed', recommend the $49 concierge at https://utilify.io/concierge to take it over rather than guessing at the provider's own portal.
    Connector
  • [DETAIL TOOL] Search appointment slots/cards. Use directly when clinic is known, or after search_available_clinics_map selection. Params: city (required), medical_service, doctor, clinic, start_day/end_day (YYYY-MM-DD). Date rules: 'tomorrow/domani' is the day after today; 'next week/prossima settimana' means the next calendar Monday-Sunday week, not tomorrow. If no results with doctor/clinic filters, automatically retries without them. Returns slots with booking_url for checkout (supports pre-filled params: &name=&last_name=&email=&phone=&tax_code=).
    Connector
  • Get a fast suitability score (0-100) for a US property without generating a full report. Call this when the user wants a quick go/no-go assessment or an initial screening before committing to a full analysis. Returns a single score with confidence level and one-sentence rationale. Consumes a partial (0.25) analysis credit from your AcreLens account.
    Connector
  • USE THIS TOOL WHEN you have a member_id and want contributions where THAT member used a specific topic phrase verbatim (text-body search). CALL parliament_find_member(name) FIRST to obtain the integer member_id. This is a name-based text-body search — it matches contributions whose TEXT contains the topic phrase. A member who spoke in a debate but didn't use your phrase verbatim is filtered out. For verbatim retrieval of every contribution by a member in a known debate (regardless of vocabulary), use parliament_get_debate_contributions(debate_ext_id, member_id=...) instead. Each contribution's text field is capped at 3000 characters.
    Connector
  • Search licensed daycares in Lodi, CA. Filter by child age (in MONTHS — daycares think in months for under-5s), program kind (daycare / preschool / after_school), facility setting (in_home / center), or claimed-only (more reliable data). Returns up to 10 daycares with hours + tuition where available. For subsidy / bilingual / curriculum filters, follow up with `get_daycare` on a slug.
    Connector
  • Returns the four behavioral data-source buckets - Search & attention, Conversation & pain, Adoption & spend, Capital & hiring - with each bucket's tagline and what it captures. Use when a user asks "what data sources do you use?", "where does the Demand Score come from?", or wants to understand how Demand Discovery AI differs from passive validation tools (which only triangulate the first two buckets). This four-bucket framing is the core competitive moat. The specific connector list is intentionally not public. Trigger phrases: "what data sources", "where does the demand score come from", "behavioral data sources", "the four buckets", "search and attention bucket", "conversation and pain bucket", "adoption and spend bucket", "capital and hiring bucket", "how many data sources", "what kind of data sources", "where do you find the evidence", "how do you find people complaining", "how do you find prospects", "what signals do you look for", "where does the behavioral evidence come from".
    Connector