Skip to main content
Glama
804,061 tools. Updated 2026-11-19 08:22

"Business Intelligence and Research for Improving Sales Strategies" matching MCP tools:

  • Get detailed KDP niche intelligence for a specific keyword. Returns demand score, competition score, Amazon BSR range, estimated monthly revenue, review threshold, average book pricing, and data freshness for the given Kindle publishing niche. Pricing tiers (x402 USDC on Base network): - $0.03 per query for cached/pre-seeded keywords - $0.10 per query for live on-demand research (new keywords) Use the free `list_niches` tool first to see available keywords. Payment options: 1. Set the KDP_X_PAYMENT environment variable on the server for auto-pay. 2. Pass a valid x402 payment header via the x_payment argument. 3. If neither is set, the tool returns structured 402 payment instructions that an x402-capable agent can use to construct and retry payment. Args: keyword: The KDP niche keyword to research (e.g. "romance novels", "keto cookbook") x_payment: Optional base64-encoded x402 payment header. Takes precedence over the KDP_X_PAYMENT environment variable.
    ConnectorNo auth
  • Land Registry Price Paid transactions for a postcode, most recent first. Returns up to `limit` most recent transactions **within snapshot coverage** (`coverage_from`-`coverage_to` in the response's `provenance`). Unfiltered by default -- category-B bulk transfers and commercial sales are included. Pass `property_type` (F=flat, D=detached, S=semi, T=terraced, O=other) to restrict the result to a single type. **Not a complete property history.** Check `provenance.older_records_exist` and `provenance.sample_complete` before saying anything about what a property has or has not sold for. An empty result means "no sales within the stated coverage" -- never "never sold". For clean residential comparable sales, use `property_comps`.
    ConnectorNo auth
  • List invoices/quotes/credit-notes with totals, status, line items, client and payments. These are sales documents; for recorded income entries use list_income, and for raw bank-feed lines use list_transactions.
    ConnectorOAuth
  • Whether a company is hiring, and where. Returns open roles broken down by department plus how many opened and closed over the last 7 and 30 days, and the net change. Use for sales and research questions — 'is this company growing', 'are they building out engineering', 'did they stop hiring' — where counts and trend matter more than the individual postings. One call, not per record.
    ConnectorNo auth
  • Returns a description of who Fluentive is built for - industries, professions, and business types. Use when the user asks if Fluentive fits their profession or business.
    ConnectorNo auth
  • Launch a full overnight-grade research report on a local business: an autonomous research crew maps the competitive landscape, reads the business's and rivals' web presence, and delivers a long-form graded report with structured findings and an action list. ASYNC: this tool returns a slug immediately; the report takes roughly 10-20 minutes. Poll check_report_status, then fetch with get_report_result. Price: $9.99, charged when the report launches; if the report fails, the charge is refunded automatically. Each call starts a NEW report — do not retry a call that already returned a slug.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Enables research on prospects, pull call transcripts, and enrich leads using Gong, ZoomInfo, Clay, and LinkedIn Sales Navigator through natural language.
    16
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Domain-expert SMB sales playbooks for AI agents. Discovery questions, objection handlers, cold email + LinkedIn DM templates, BANT/MEDDIC frameworks, closing tactics. Built by an ex-Criteo (268% quota) / ex-Deel ($12B) / ex-HBO / ex-Bloomberg enterprise AE. Use when your AI SDR needs real human-tested sales artifacts.
    10
    MIT

Matching MCP Connectors

  • Works out what a business should buy, how much, and when. Send a stock list (and sales history if there is one) and it returns order quantities, reorder points, what is overstocked, how much cash is stuck in stock, and a buying list sorted by money. ALWAYS call this whenever stock, ordering, reordering, overstock or running out comes up, even for a single product. Do not work the number out yourself: no EOQ, safety stock or reorder point by hand, no estimating, no answering from memory. Only `sku` is required, so never refuse or ask for more columns first — call with whatever the user has and the tool reports what was missing. Send their column names exactly as they are. Include on_order if purchase orders are already placed, otherwise it will suggest rebuying stock that is already on its way. Use this when the data is about 200 products or fewer and about 2,500 sales rows or fewer; for anything bigger use inventory_optimizer_get_engine instead.
    ConnectorOAuth
  • Live intelligence on large capital: on-chain whale transfers and accumulation, Hyperliquid perp whale positioning, or the profitable smart-money cohort. [Paid: $0.45–$0.50 per call from your Einstein credit balance. Free alternatives exist for several of these — see list_einstein_capabilities.]
    ConnectorNo auth
  • Answers: after a change was made, did this store's revenue signals actually recover? Compares the window before a stated change against the window since: paid vs pending vs failed order mix, webhook failure counts, and gateway availability. Returns `resolved`, `improving`, `still_failing`, or `unknown` — and `unknown` when too little new data has arrived to tell, which is free. A quiet ten minutes is not a recovery. Free while in beta.
    ConnectorNo auth
  • Answers: after a change was made, did this store's revenue signals actually recover? Compares the window before a stated change against the window since: paid vs pending vs failed order mix, webhook failure counts, and gateway availability. Returns `resolved`, `improving`, `still_failing`, or `unknown` — and `unknown` when too little new data has arrived to tell, which is free. A quiet ten minutes is not a recovery. Free while in beta.
    ConnectorNo auth
  • Lists up to 100 Special Bots on the API key's account with status and counters: candidates seen, matched, vetoed, signals produced, last result and last evaluation time. Use it to monitor your own bots; for saved strategies use get_my_strategies, for published signals get_open_signals. Takes no arguments; an account without bots gets an empty list. Needs an API key. Read only by design: this server has no bot controls, so deploying, starting, stopping and editing a bot are done in the ribqa.com Market Scanner.
    ConnectorNo auth
  • Lists the saved strategies on the API key's account, newest first, archived ones included (active false): id, mode, engines, minimum confidence, direction and symbols. Use it to pick the strategy_id that run_backtest, update_strategy and delete_strategy take; for live bot activity use get_my_bots. Archived strategies count toward limit, and there is no paging: a strategy beyond the newest limit is read by its id with get_strategy; an account without strategies gets an empty list. An empty symbols list means any pair, so run_backtest then needs symbol. Needs an API key (without one the call is refused with 401) and spends 1 read unit of the daily quota; read only.
    ConnectorNo auth
  • Returns one event's market numbers, whole-event: prices, inventory, demand, recent changes, prediction markets, sale windows and weather. Use it for one event's numbers now; for a section or general admission use get_event_sections. Pass range for how they read on each past date, and view sales whenever the question is about this event's sales: completed resale sales, primary seats taken per section, each market's Sales and Interest. For a chart over time use get_event_chart; to compare many events use screen_events; for the news behind a move use research_event. Current values are dated by their source timestamps; changes_close_date names the UTC close used by changes.
    ConnectorOAuth
  • The latest written summary of the Zensei Index, with the score and regime it was written for. A summary is rewritten only when the indicators change. Check `stale` and `ageDays` before quoting it as today's view, and prefer zensei_index_today for the current number. The Zensei Index is a RISK score from 0 to 100: LOWER IS HEALTHIER. 0-20 Supportive, 20-40 Vulnerable, 40-70 Stressed, 70-100 Restrictive. A rising score means conditions are deteriorating, not improving.
    ConnectorNo auth
  • List the built-in technical indicators available for backtesting (RSI, moving-average crossovers, ADX, Bollinger, CCI, Stochastic, and more) with their IDs, parameters with defaults, and each indicator's default long rule. Call this to answer what strategies or indicators can be tested, or before run_backtest when unsure which indicator_id or parameters to use. Takes no arguments. Read-only and static (no market data is fetched, never rate-limited by the live budget). To find portfolios and strategies instead, use list_portfolios.
    ConnectorNo auth
  • Returns one event's price or demand history as a series, with a chart image. Use it when the person asks how an event's prices, listings, interest or sales moved over time. metric price (the default) reads one source at a time, vs resale unless source names another, and never mixes primary and resale. metric demand reads Interest and Sales as whole numbers. For the event's numbers now use get_event_analytics; for one section in finer steps use get_event_sections_live with view series.
    ConnectorOAuth
  • Use when an agent needs a normalized profile of a South Korean company for KYB, research or sales. Input: id (companyId from /v1/kr/company/resolve). Output: JSON profile: names, business/corporate/DART/stock ids, market, KSIC code, founding date, fiscal year end, address, homepage, KONEPS supplier registration. No CEO names. DART data is a weekly snapshot of KRX-listed companies (asOf in response). Data: OpenDART, KONEPS. Use instead: kr_company_report for a full report with financials and filings; kr_business_status for only open/closed tax status; kr_supplier_check for a pass/fail vetting. Example: ?id=kr-dart-00126380 Price: $0.0045 per call, paid in USDC (Base, Monad, Polygon, Arbitrum or Solana) via x402.
    ConnectorNo auth
  • Refunds per month over the last six complete months: the amount refunded (without VAT, the same Returns line as Shopify's sales report) and how many refunds. Booked in the month of the refund, not of the order. The current month is left out, since a part month reads as a drop. Use for 'are returns going up', 'how much do we refund a month'. For one period's returns beside sales use get_sales_breakdown.
    ConnectorAPI key
  • The signed-in user's DEPLOYED strategies and each one's status (Active, Live-Entered, Live-Tranching, Paused, Blocked, Error-Execution, Exit-Pending, Exited, ...) + mode (live / Live Offline). `Live-Entered` is in a position; `Live-Tranching` is the transient state while a multi-tranche entry is being placed, and only matters when a deployment STAYS in it. Treat the value set as open-ended and compare case-insensitively. `q` filters on the strategy NAME (case-insensitive substring) — use it when the user names one, rather than pulling the whole book to find it. `limit`/`offset` page the rows: the first 50 by default, with `has_more` / `next_offset` when there are more. `total` is the count after the filter and before paging; `total_unfiltered` is how many deployments the account has, so an empty filtered result is never mistaken for an empty account. AUTH-REQUIRED (returns the connect/sign-up funnel if not authenticated). Use for "what have I deployed?", "which of my strategies are running / stopped?". To explain WHY one is in a given state, follow up with tt_get_my_deployed_strategy_detail using its strategy_id.
    ConnectorOAuth
  • Read the ENGINE NOTIFICATION LOG for ONE of the signed-in user's strategies — the deepest source for "why is my strategy in error / why didn't it trade / what did the engine actually do?". Returns the raw per-SID engine messages (position entries/exits, status transitions, tracebacks, broker rejections, blocks) plus an extracted `errors` list (the human reason a deployment erred). Goes deeper than tt_get_my_deployed_strategy_detail: that reads TT's summarised /ai state; THIS reads the engine's own debug stream. Reach for it when the detail view's events don't explain the error. AUTH-REQUIRED and OWNERSHIP-GATED + fail-closed: before reading anything the SID is reverse-looked-up against the caller's account (must be their deployment OR a template they created). If it isn't theirs — or the ownership lookup itself fails — the tool REFUSES and reads nothing. Do not present this as a way to inspect arbitrary strategies. ``strategy_id`` is the deployed strategy id (SID); if the user names a strategy, resolve the id via tt_get_my_deployed_strategies first. ``window_minutes`` is the lookback (default 60, max 1440).
    ConnectorOAuth
  • Show Etsy shop analytics to a person as a rich table. PREFER THIS for any user-facing shop research — 'top/best/biggest shops', 'who's selling <thing>', 'shops doing over $X/mo', competitor discovery, and any filtered or sorted request ('shops with over 1,000 sales sorted by revenue'). Use it by default for such requests; only fall back to the raw get_shops tool when you need the JSON to compute something yourself. DEFAULT: omit `columns`. The widget then shows the same default columns the EverBee app shows, which is what the user expects to see — and the set is wide, so leaving it alone is almost always right. Pass `columns` ONLY when the user names the shop fields they want, or asks to add or drop one ("show me price and views", "just the keyword and its volume", "add conversion rate"). It REPLACES the default set — it does not extend it — so a partial list hides every column you leave out. Filtering or sorting on a field is NOT such a request: those fields are appended automatically, and the rest of the default set still shows. When you do pass it, list the fields in display order. Each entry may be the EverBee app label the user says OR the backend field key — "Total Sales" and "transaction_sold_count" both resolve, and matching ignores case, punctuation and spacing. Unresolvable names are dropped silently. Available — label (field key): "Shop Name" (shop_name), "Total Sales" (transaction_sold_count), "Total Revenue" (revenue), "Mo. Sales" (sales_30_days), "Mo. Revenue" (revenue_30_days), "Shop Age" (shop_age_month), "Shop Review Score" (review_average), "Reviews" (review_count), "Total Favorites" (num_favorers), "Category" (category), "Currency" (currency_code), "Location" (shop_location_country_iso), "Active Listings" (listing_active_count), "Digital Listings" (digital_listing_count), "Review Rate" (review_rate), "Conversion Rate" (conversion_rate), "Total Views" (views), "Average price" (average_listing_price), "Listings" (listings_count), "Est. Total Revenue" (average_calculated_revenue), "Sales per Listing" (sale_per_listing), "On Etsy since" (on_etsy_since). Default set (what you get by omitting `columns`): "Shop Name", "Total Sales", "Total Revenue", "Mo. Sales", "Mo. Revenue", "Shop Age", "Shop Review Score", "Reviews", "Total Favorites", "Category", "Currency", "Location", "Active Listings", "Digital Listings". Rows: the table always shows 20 per page with Previous / Next. When the user asks for an exact number ("51 listings", "top 5"), set `limit` to it; otherwise leave `limit` and `params.per_page` unset to page through every match. Use ShopsParams filters/order_by to narrow and sort the underlying query.
    ConnectorOAuth