Skip to main content
Glama
603,140 tools. Updated 2026-09-23 15:07

"Tools and methods for creating charts and graphs" matching MCP tools:

  • Call this first for every XGR purchase. Read live price, stock and payment assets; use payment_assets[].key exactly as payment_asset and inspect requires_sender_wallet before creating an order.
    ConnectorNo auth
  • Get stored end-of-day OHLCV candles for a stock, ETF, or crypto ticker, daily or weekly. Use this for exact-return calculations, charts, and backtests after get_summary identifies a setup. Results are paginated; pass next_cursor back as cursor to continue. Equity and ETF bars are split-and-dividend adjusted; crypto bars are unadjusted. Credit cost is 1 credit per 100 bars returned, rounded up, with a 1 credit minimum.
    ConnectorNo auth
  • Find every flow and block whose contents contain a keyword. Read-only. Searches message text and its translations, button labels and URLs, action names and configs, action input/output field paths and values, condition operands, trigger commands and payloads, custom-code files, and flow names and descriptions. A keyword matching a VARIABLE NAME also returns the blocks that reference that variable, which plain text search cannot do because blocks store variable ids, not names. Use this instead of walking flows with get_flow_context when you know what the content says but not where it lives. Broadcast-backed flows and operation graphs are excluded — use list_broadcasts and the operations tools for those.
    ConnectorNo auth
  • Answers ONE question: is stress reaching US household credit? Use corporate_transmission_board for firms. Delinquency, charge-offs, revolving credit and unscored debt-service context; gaps stay in cannot_see. Display-only; no institution score or watchlist tier. full:true adds methods and histories.
    ConnectorNo auth
  • Return a compact application, flow, sequence, operation, and bot summary — the cheapest way to orient in a workspace. Read-only, no side effects. Deliberately omits variables and full flow graphs: use get_variable_context for variables, get_flow_context for a flow's topology, and get_application_context when you need flows, bots, and variables together.
    ConnectorNo auth
  • Two players side by side: identity, account age, visibility, Steam bans, FACEIT and shared friends (compared over the full friend lists). HEAVIEST tool - it builds two summaries plus both friend graphs; for a single player prefer steam_summary.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to connect to a privacy-first, self-hostable workout planning and training log, allowing coaching agents to preview and apply program changes while accessing training data through OAuth-protected endpoints.
    AGPL 3.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to interact with Databricks workspaces, running SQL queries, managing jobs, and exploring schemas via the Model Context Protocol.
    1
    GPL 3.0

Matching MCP Connectors

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

  • Energy-Charts (Fraunhofer ISE) MCP — European electricity generation, prices, and capacity.

  • Compares two birth charts: the major aspects between one person's Sun, Moon, planets and North Node and the other's, each with its orb. Use it when a person asks how two charts relate, which aspects run between two people's charts, or what one person's planet does to another's. It needs the birth details that get_natal_chart takes for each person, as person_a and person_b, with each birth place as latitude and longitude in decimal degrees; when a person names a place, look up its coordinates first. There is no score: the result is the aspects themselves. Houses and angles are not compared. Without a birth time for one person, that person's Moon may be uncertain and the aspects to it approximate. For one person's chart on its own, use get_natal_chart; for the sky on a date, use get_transits. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).
    ConnectorNo auth
  • Runs the Tamil ten-porutham checklist for two charts, counts passes out of ten, surfaces Rajju/Vedha classical condition booleans, and returns per-porutham evidence objects. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per native. AFTER: asterwise_get_thirumana_porutham — extended twelve-koota read if needed. INPUT CONTRACT: Two BirthData objects per global contract. DO NOT CONFUSE WITH: asterwise_get_thirumana_porutham — twelve poruthams including Nadi and Varna, not ten. asterwise_get_dashakoot — South Indian float scoring, not Tamil pass grid. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-porutham/
    ConnectorOAuth
  • Midpoint composite chart for two people. Each composite planet is the midpoint of the two natal positions. Returns composite planets with dignities and internal aspects. WORKFLOW: BEFORE: asterwise_get_western_synastry — examine inter-chart aspects before composite. AFTER: None. INPUT CONTRACT: person1, person2 — WesternBirthData each. house_system ignored. DO NOT CONFUSE WITH: asterwise_get_western_synastry — two charts, inter-chart aspects vs composite (one midpoint chart). asterwise_get_western_compatibility — numeric score vs structural composite chart. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-composite/
    ConnectorOAuth
  • Search the CDC dataset catalog by keyword, category, or tag. Returns IDs, names, truncated descriptions, asset types, column counts, and update timestamps. The catalog also holds charts, maps, stories, files, and links; an entry whose columnCount is 0 is one of those and yields no data from the other tools. Use cdc_get_dataset_schema for the full column list of a chosen dataset.
    ConnectorNo auth
  • Call this first. Returns how to use Précis over this connector: the data model (scenarios, metrics, statements, dimensions), the reporting-tool variants, and how to build charts. Read it before composing queries.
    ConnectorNo auth
  • List the saved payment methods (used only to pay for flight bookings, not for cards or adding funds). Returns each method with its id, brand, last 4 digits, and expiry, and marks the default one. Use setup_payment_method to add a new one. The gated tools set_default_payment_method and remove_payment_method also exist; call them by name even though they aren't in the tools list.
    ConnectorNo auth
  • Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
    ConnectorNo auth
  • Runs the Tamil ten-porutham checklist for two charts, counts passes out of ten, surfaces Rajju/Vedha classical condition booleans, and returns per-porutham evidence objects. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per native. AFTER: asterwise_get_thirumana_porutham — extended twelve-koota read if needed. INPUT CONTRACT: Two BirthData objects per global contract. DO NOT CONFUSE WITH: asterwise_get_thirumana_porutham — twelve poruthams including Nadi and Varna, not ten. asterwise_get_dashakoot — South Indian float scoring, not Tamil pass grid. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-porutham/
    ConnectorOAuth
  • Midpoint composite chart for two people. Each composite planet is the midpoint of the two natal positions. Returns composite planets with dignities and internal aspects. WORKFLOW: BEFORE: asterwise_get_western_synastry — examine inter-chart aspects before composite. AFTER: None. INPUT CONTRACT: person1, person2 — WesternBirthData each. house_system ignored. DO NOT CONFUSE WITH: asterwise_get_western_synastry — two charts, inter-chart aspects vs composite (one midpoint chart). asterwise_get_western_compatibility — numeric score vs structural composite chart. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-composite/
    ConnectorOAuth
  • Compare two saved people's Human Design charts for relationship dynamics. Computes electromagnetic, companionship, compromise and dominance channels, composite type and authority, center dynamics, connection theme, profile compatibility, and bridging gates: `split_definition_bridges` lists the gates each person provides to bridge the other's split definition, and `composite_bridge_gates` the gates neither holds that would bridge the composite's split. Use it for any question about how two people fit rather than comparing charts yourself; it also renders the connection view the user sees. Both people must be saved (or 'me'). If one is not, saving them is part of the request: call save_person with the data the user gave, compare, and say you saved them.
    ConnectorOAuth
  • Reference lists for creating a survey: countries available for fielding (code + name), survey languages, topic categories, and the wallet currency. Call this before create_survey to pick valid country_code / category values.
    ConnectorOAuth
  • Call ANY Solana-compatible JSON-RPC method by name — full RPC surface beyond the typed solana_* tools (getProgramAccounts, getBlock, getEpochInfo, simulateTransaction, ...). Defaults to Solana mainnet; pass network:slonana to query Slonana (rpc.slonana.com), which additionally exposes RPC methods no other network has: getAlpenglowHealth (consensus migration status), getBridgeStatus, getAexchanRelays, getValidatorStats, quote. (listSvmNetworks/enableSvmNetwork/disableSvmNetwork/setNetworkRpcUrl also exist but are inert API-compat stubs — listSvmNetworks always reports one hardcoded network and the enable/disable/set calls ignore their arguments and return true; verified in source, not live network-management controls.) For tools that exist ONLY on Slonana's MCP server with no RPC-method equivalent (the aea_* agent registry), use mcp_call instead.
    ConnectorNo auth
  • Resolve the caller's identity from their API key or OAuth token. Call this FIRST when the user asks about "my graph" but has not provided a graph ID. For a graph/service key, `me` resolves to a Graph: use `id` as the graphId and `variants[].name` as the variant for the graph-scoped health-check tools, so the user does not have to supply either. For a user (personal key or OAuth), `me` resolves to a User instead: there's no single graph, so each org membership's `graphs[].id` / `graphs[].variants[].name` lists the graphId/variant options the graph-scoped tools need, across every org the user belongs to. Also handles service-account keys.
    ConnectorNo auth
  • Checkout methods open right now: "crypto" (a hosted invoice: BTC, ETH, TRX, USDT), "card", and "wallet" (a prepaid balance, see create_wallet). `gateways` names the providers behind each method; a checkout that does not ask for one by name goes to the first, which is what these tools do.
    ConnectorNo auth