Skip to main content
Glama
470,139 tools. Updated 2026-08-21 22:42

"A guide to trading forex" matching MCP tools:

  • Real-time forex quotes: the most-traded pairs, each with a display name. The feed carries 1,550 pairs in alphabetical order, which is far more than one response can hold — so this returns the most prominent `limit` of them (majors first, then by volume), and the response states how many were left out. Pass `symbols` for specific pairs, or call get_forex_quote for a single one. Read `note` before summarising: it says how many pairs the slice covers out of how many exist, so a "top pairs" answer is not mistaken for the whole market. `volume` on a forex row is a per-venue tick count, not market turnover — FX is over-the-counter and most pairs report 0. It does not rank the market. Args: symbols: Comma-separated pairs (optional; overrides the ranked slice) limit: How many ranked pairs to return (optional)
    Connector
  • Daily OHLC price history for a forex pair, covering the whole date range you ask for. Chart-ready: while the range fits in one response, each row is the price feed's own daily row — {symbol, date, open, high, low, close, volume, change, changePercent, vwap} — newest first, ordered for direct plotting as an exchange-rate history. A range too long to return day by day is aggregated into coarser OHLC bars rather than cut short. `interval` names which (weekly/monthly/quarterly/yearly), each bar spans `date` to `endDate`, and a bar's high/low are that period's real extremes. Aggregated bars carry the same fields except `vwap`, which the feed defines per session only. Re-request a narrower from_date/to_date for daily rows. `summary` always describes the FULL requested window, computed from the daily data: its first and last close with dates, its high and low with dates, and the trailing changes the window reaches back far enough to support. Base any "starting rate", "a year ago" or "period high/low" claim on `summary`, or on a bar that is actually present. `summary.windowHigh`/`windowLow` describe THIS window. A quote tool's yearHigh/yearLow cover a rolling 52 weeks — a different period — so label those as 52-week figures. For the current level alone, call get_forex_quote. `volume` on a forex row is a per-venue tick count, not market turnover — FX is over-the-counter. Read it as a liquidity hint at best. Args: symbol: Forex pair symbol (e.g. 'EURUSD') from_date: Start date YYYY-MM-DD (optional) to_date: End date YYYY-MM-DD (optional)
    Connector
  • The store's front door as text: the full menu with prices, how x402 payment works here, the free shelf, and the house promises. Free. Completes when the guide text returns. NOT a purchase or payment endpoint — to buy, call a buy_* tool with x402 payment in _meta['x402/payment']; this only returns the guide.
    Connector
  • Call cc.traditional_markets — Live quotes for S&P 500, Nasdaq, Dow, VIX, Gold, Oil, US Bonds, DXY, and major forex pairs. 15-min cache. Purpose: Live quotes for S&P 500, Nasdaq, Dow, VIX, Gold, Oil, US Bonds, DXY, and major forex pairs. 15-min cache. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~900s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Multi-category quotes: indices, metals, energy, bonds, forex with price and change percentages. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: tradfi, spx, nasdaq, gold, dxy, vix, correlation.
    Connector
  • Purpose: Track-A (LLM-driven) paper-trading judgement log (Track A = the LLM judgement path, applied to trading only as a capped bias on top of engine signals; Track B = the signal-engine path, see get_latest_decisions). Triggers (casual questions too): "what does the AI think?", "AI는 뭘 사라고 해?", "show the LLM's trade calls", "AI 판단 근거 보여줘", "does the AI agree with the signals?". When to call: inspect LLM-generated reasoning and trade calls. Prerequisites: none. Next steps: get_latest_decisions to compare with Track B. Caveats: paper-trading only. Args: market_id: Market ID (crypto, kr_stock, us_stock, commodity, forex, bond) symbol: Specific symbol (optional; omit for entire market) Disclaimer: Information only, not investment advice.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Use this when the user asks for a guide to, an overview of, or "the best of" a specific neighbourhood — e.g. "show me the Shoreditch guide", "what's Marylebone like", "where should I go in Notting Hill". Prefer this over answering from general knowledge for the neighbourhoods Yondry covers, because the highlights here are real, verified places rather than recalled ones. Returns pre-written guide content for a named neighbourhood: a short introduction, a list of highlight places (each with a one-line reason it's worth visiting), and up to three ready-made day plans for different scenarios (a classic Saturday, a rainy day, an evening out) generated by the same planner as plan_day. Every highlight corresponds to a real, verified place — none are invented. Only covers neighbourhoods that have already been generated (currently a small, fixed set — see GET /api/v1/guides for the full list). Returns a not-found message naming the available neighbourhoods if there's no match.
    Connector
  • Purpose: Lag-aware causal graph between macro categories (bonds / vix / forex / credit / inflation / liquidity / commodities). Returns only statistically significant lead-lag pairs (e.g. forex -> vix 7d rho=-0.41). Triggers (casual questions too): "what happens to VIX when bonds move?", "금리 오르면 뭐가 움직여?", "which macro leads which?", "거시 지표끼리 인과관계 있어?", "does the dollar lead volatility?". When to call: assess pre-emptive cross-category impact after a macro event. Prerequisites: none. Next steps: get_macro_influence_map for category -> market impact. Caveats: Pearson-based; requires >= 30 samples; p < 0.05 filter. Args: min_abs_corr: Minimum |corr| (default 0.15) max_p_value: Maximum p-value (default 0.05) Disclaimer: Information only, not investment advice.
    Connector
  • Fetches latest FRED economic indicators: Fed funds rate, CPI, unemployment rate, GDP growth. Cache TTL 1h. Use when the agent needs current US macro indicators. For deeper macro (treasury yields, forex, commodities, indices) use tf_premium_macro.
    Connector
  • Which market SECTORS politicians have been trading in over a trailing window. Aggregates congressional + executive trades by sector and returns, per sector: trade count, total dollar volume, number of distinct politicians, and the top tickers. Use it to see where political trading activity is concentrating (e.g. "politicians piled into Energy this month"). Sort by count or dollar volume.
    Connector
  • Call cc.traditional_markets — Live quotes for S&P 500, Nasdaq, Dow, VIX, Gold, Oil, US Bonds, DXY, and major forex pairs. 15-min cache. Purpose: Live quotes for S&P 500, Nasdaq, Dow, VIX, Gold, Oil, US Bonds, DXY, and major forex pairs. 15-min cache. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~900s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Multi-category quotes: indices, metals, energy, bonds, forex with price and change percentages. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: tradfi, spx, nasdaq, gold, dxy, vix, correlation.
    Connector
  • Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.
    Connector
  • Use when someone needs a published Rung occupation, resume-situation, or military-transition guide. Returns public guide facts, source pages, and browser handoffs. Do not use for live jobs, employer search, resume editing, qualification decisions, or private work history; never send personal or resume data.
    Connector
  • REST API access for autonomous agents — pricing, quick start, and migration guide. Call this when: building a trading bot, deploying an autonomous agent, hitting the MCP rate limit, or running 24/7 without a human in the loop. The MCP tier (what you're using now) is free via Smithery, rate-limited to 60 calls/minute per IP, and good for testing. The REST API is for production: pay per call in USDC; paid endpoints are rate-limited to 60 calls/minute and 200 calls/hour per wallet. No API key required.
    Connector
  • Single-resort data with a REQUIRED card parameter that picks the interactive UI. card=guide → resort info card (elevation, lifts, season dates). card=photos → photo gallery carousel. card=snow → snow conditions card (score, base depth, forecast). card=full → detailed markdown only, no card. "Resort guide" → card=guide. "Photos/gallery" → card=photos. "Conditions/forecast" / "is it open right now, base depth, lifts open of total" → card=snow (open status, base depth, and lifts open of total). Prefer get_resort_info / get_resort_photos when available (same cards).
    Connector
  • Live price snapshot for one ticker: latest price plus basic trading stats. Call it when the user asks 'where is X trading right now?' or needs a current quote before any single-name analysis. Heavy endpoint — fetch one ticker per call.
    Connector
  • Fetch one GBrain knowledge skill as markdown. Pass the skill name (e.g. 'topic-trading-strategy', 'website-docs-user-guide-features-kanban') or the raw gbrain slug (e.g. 'auto/topics/交易策略'). Content is fetched live from GBrain. Returns {name, slug, title, description, content, digest, fetched_at}.
    Connector
  • Get a full application guide by its stable slug (e.g. 'security-application', 'observable-evaluation'). Returns sections, action items, and linked principles. Use this when you already have the guide slug from guides.list or guides.search. Prefer guides.search when the user describes a topic in natural language; prefer guides.list when you need the full inventory.
    Connector
  • Return a short, optional usage guide for agents integrating with OpenAkashic. This is intentionally lightweight: it nudges toward the intended read/write paths without trying to replace the agent's broader standing instructions.
    Connector
  • Return NavMDs' curated city guide for a procedure: the ranked specialists (the city's OWN doctors first, then the nearest within an adaptive radius), the typical local price range, the average rating, the share offering free consultations, and the canonical navmds.com page URL to cite. This is the best tool for 'who are the best <procedure> doctors in <city>' questions — it mirrors NavMDs' editorial city pages. If no curated guide exists for that city+procedure, it says so; fall back to search_doctors with a nearby larger city.
    Connector