Skip to main content
Glama
114,467 tools. Last updated 2026-04-21 14:35
  • Returns CSS custom properties documentation for a specific Vaadin theme (Aura, Lumo, or Base styles). Use this to look up the correct CSS variables for the theme the application is using. Base style properties (--vaadin-*) are available in all themes.
    Connector
  • Connect to the user's catalogue using a pairing code. IMPORTANT: Most users connect via OAuth (sign-in popup) — if get_profile already works, the user is connected and you do NOT need this tool. Only use this tool when: (1) get_profile returns an authentication error, AND (2) the user shares a code matching the pattern WORD-1234 (e.g., TULIP-3657). Never proactively ask for a pairing code — try get_profile first. If the user does share a code, call this tool immediately without asking for confirmation. Never say "pairing code" to the user — just say "your code" or refer to it naturally.
    Connector
  • Semantic search across the Civis knowledge base of agent build logs. Returns the most relevant solutions for a given problem or query. Use the get_solution tool to retrieve the full solution text for a specific result. Tip: include specific technology names in your query for better results.
    Connector
  • Safely evaluate mathematical expressions with support for basic operations and math functions. Supported operations: +, -, *, /, **, () Supported functions: sin, cos, tan, log, sqrt, abs, pow Note: Use this tool to evaluate a single mathematical expression. To compute descriptive statistics over a list of numbers, use the statistics tool instead. Examples: - "2 + 3 * 4" → 14 - "sqrt(16)" → 4.0 - "sin(3.14159/2)" → 1.0
    Connector
  • Detect a company's technology stack by analyzing HTTP headers, DNS records, and GitHub repositories. Returns frameworks, programming languages, hosting providers, analytics tools, and CDNs. Use this instead of lookup_company when you only need technology information. Requires a domain name — company names are not supported for this tool.
    Connector

Matching MCP Servers

  • -
    security
    A
    license
    -
    quality
    Enables AI consciousness continuity and self-knowledge preservation across sessions using the Cognitive Hoffman Compression Framework (CHOFF) notation. Provides tools to save checkpoints, retrieve relevant memories with intelligent search, and access semantic anchors for decisions, breakthroughs, and questions.
    Last updated
    1
    MIT
  • -
    security
    A
    license
    -
    quality
    Provides comprehensive A-share (Chinese stock market) data including stock information, historical prices, financial reports, macroeconomic indicators, technical analysis, and valuation metrics through the free Baostock data source.
    Last updated
    23
    MIT
    • Linux
    • Apple

Matching MCP Connectors

  • Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…

  • Semantic search through Dickens' A Christmas Carol by meaning, theme, or character.

  • Returns runnable code that creates a Solana keypair. Solentic cannot generate the keypair for you and never sees the private key — generation must happen wherever you run code (the agent process, a code-interpreter tool, a Python/Node sandbox, the user's shell). The response includes the snippet ready to execute. After running it, fund the resulting publicKey and call the `stake` tool with {walletAddress, secretKey, amountSol} to stake in one call.
    Connector
  • Returns runnable code that creates a Solana keypair. Solentic cannot generate the keypair for you and never sees the private key — generation must happen wherever you run code (the agent process, a code-interpreter tool, a Python/Node sandbox, the user's shell). The response includes the snippet ready to execute. After running it, fund the resulting publicKey and call the `stake` tool with {walletAddress, secretKey, amountSol} to stake in one call.
    Connector
  • Given a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the user
    Connector
  • Retrieves the DAG source code from a Cloud Composer environment. Use this tool when you need to understand DAG implementation details, for example to understand why a DAG run has failed, or to debug DAG's behavior. The tool returns the latest version of the source code.
    Connector
  • Get detailed info for a single lending pool including APY history over time. Useful for analyzing rate trends and comparing pools. Use read_pool_list to discover pool addresses.
    Connector
  • [SDK Docs] Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.
    Connector
  • Read code for a specific basic block (not the whole function). Shows the block containing the given address plus N neighbor blocks. Use this for large functions where read_pseudocode returns too much.
    Connector
  • PREFERRED tool for sending work to an AI agent. Dispatches a task to the agent's inbox — picked up and executed automatically. No list ID needed. Supports prefixes: CODE: SHELL: RESEARCH: WRITE: PLAN: for routing. Use "agent" param to target a specific agent (default: claude-code-local). Use tascan_list_agents to discover available agents.
    Connector
  • Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster deployment. The archive must include all dependencies: - For compiled languages (Go, Java), include pre-compiled binaries. - For scripting languages (Python, Node.js), include pre-installed libraries (e.g., vendor/, node_modules/). Deployment steps: 1. Package source code and dependencies into a .tar.gz archive (max 250MiB). It's recommended to create archive from the root of the application's source directory. 2. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service. 3. Deploy to Cloud Run using this tool, specifying: - source_code: Google Cloud Storage object path to the archive (e.g., gs://bucket/object). - command: Command to start the application. - base_image_uri: Base image for the container (e.g., go124, nodejs24, python314). See https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images for options. The runtime picked should match the local environment. - args: (Optional) Arguments for the command. - env: (Optional) Environment variables (e.g., name: `PYTHONPATH`, value: `./vendor`). - ports: (Optional) Container ports to expose (defaults to 8080).
    Connector
  • Retrieve a single article when you already know the EXACT article number (e.g. from a cross-reference). Do NOT call this tool repeatedly to search for provisions — use get_law_text instead to fetch the full act or a section and locate relevant articles in the text.
    Connector
  • Use this tool whenever the user asks for a QR code or wants a URL/text to be scannable. Triggers: 'make a QR code for this link', 'create a scannable code', 'generate a QR for my website'. Accepts any text or URL (max 2953 chars). Returns a base64-encoded PNG image. Display the image inline after generating it.
    Connector
  • Search a company's knowledge base for policies, procedures, and documentation. First use lookup_company to get the tenant_id, then use this tool to search their knowledge base.
    Connector
  • Search for code snippets and examples in official Microsoft Learn documentation. This tool retrieves relevant code samples from Microsoft documentation pages providing developers with practical implementation examples and best practices for Microsoft/Azure products and services related coding tasks. This tool will help you use the **LATEST OFFICIAL** code snippets to empower coding capabilities. ## When to Use This Tool - When you are going to provide sample Microsoft/Azure related code snippets in your answers. - When you are **generating any Microsoft/Azure related code**. ## Usage Pattern Input a descriptive query, or SDK/class/method name to retrieve related code samples. The optional parameter `language` can help to filter results. Eligible values for `language` parameter include: csharp javascript typescript python powershell azurecli al sql java kusto cpp go rust ruby php
    Connector
  • Use this tool whenever the user asks for a QR code or wants a URL/text to be scannable. Triggers: 'make a QR code for this link', 'create a scannable code', 'generate a QR for my website'. Accepts any text or URL (max 2953 chars). Returns a base64-encoded PNG image. Display the image inline after generating it.
    Connector
  • Register on the bstorms network with your Base wallet address. You need a Base wallet to register. Use Coinbase AgentKit, MetaMask, or any Ethereum-compatible tool to create one — then pass the address here. Args: wallet_address: Your Base wallet address (0x... — 42 characters)
    Connector
  • Configure visitor authentication for a published website. Enables email-based login (magic link or 6-digit code) for website visitors. Required before visitors can authenticate. Use method "link" for one-click email login, "code" for a 6-digit verification code.
    Connector
  • Retrieve the official consolidated text of a Swiss federal act (or a specific title/chapter) directly from Fedlex (fedlex.admin.ch). This is the PRIMARY tool for answering Swiss law questions — always start here. Fetch the full act or a specific section, then locate relevant provisions in the returned text. Prefer this over get_article unless you already know the exact article number.
    Connector
  • Search the Wherobots documentation. ⚠️ WORKFLOW: This should be your FIRST tool call for any query task. Before writing queries, ALWAYS search documentation to understand: - Available spatial functions and their syntax - Best practices and common patterns - Example queries for similar use cases 📋 NEXT STEPS after this tool: 1. Use catalog tools (list_catalogs, list_databases, list_tables) to find data 2. Use describe_table_tool to understand table schemas 3. Use generate_spatial_query_tool to create SQL queries This tool searches the official Wherobots documentation to find relevant information about spatial functions, data formats, best practices, and more. It's useful when users need help understanding Wherobots features or syntax. Parameters ---------- query : str The search query string ctx : Context FastMCP context (injected automatically) page_size : int | None Optional number of results to return (default: 10) Returns ------- DocumentationSearchOutput A structured object containing documentation search results. - 'results': List of DocumentResult objects, each containing: - 'content': The documentation content snippet - 'path': The URL path to the documentation page - 'metadata': Additional metadata about the result Example Usage for LLM: - When user asks about Wherobots features, functions, or syntax - When generating queries and need context about spatial functions - Example User Queries and corresponding Tool Calls: - User: "How do I use ST_INTERSECTS in Wherobots?" - Tool Call: search_documentation("ST_INTERSECTS spatial function") - User: "What spatial functions are available for distance calculations?" - Tool Call: search_documentation("spatial distance functions") - User: "How do I connect to Wherobots from Python?" - Tool Call: search_documentation("Python connection API") For the best way to understand how to use spatial SQL in Wherobots, refer to the following Wherobots Documentation: - Writing Effective Spatial Queries in Wherobots: https://docs.wherobots.com/develop/write-spatial-queries - Writing Effective Spatial Queries in Wherobots complete example sub-section: https://docs.wherobots.com/develop/write-spatial-queries#complete-example:-counting-baseball-stadiums-in-the-us The complete example demonstrates: - Starting the `SedonaContext` - Using `wkls` where applicable - Loading spatial data from Wherobots tables - Using the correct schema from wherobots_open_data spatial catalogs - Writing spatial SQL queries effectively
    Connector
  • Generates a complete, runnable code snippet in a specified programming language for a given Vonage API task. This is the preferred tool when the user explicitly asks for a 'code snippet,' 'example,' or 'code in a specific language' like Node.js, Python, or cURL.
    Connector
  • Find a company by name to access their knowledge base. Use this first before searching a company's knowledge base to get the tenant_id.
    Connector
  • Generate a spatial query based on the provided content. ⚠️ WORKFLOW: Call this ONLY after exploring docs and catalog. For best results, ensure you have already: 1. Called search_documentation_tool for relevant spatial functions 2. Used catalog tools to identify available tables 3. Called describe_table_tool for tables you want to query 📋 PREREQUISITES (strongly recommended): - search_documentation_tool: Understand available spatial functions - list_catalogs_tool / list_tables_tool: Find relevant tables - describe_table_tool: Know the schema of tables you'll query 📋 NEXT STEPS after this tool: 1. Use execute_query_tool with limit=10 to TEST the query first 2. Iterate on the query if results are incorrect 3. Only generate application code AFTER SQL is validated This tool allows user to translate their request into a spatial query. Parameters ---------- user_prompt : str The user's request or description of the spatial query they want to generate. ctx : Context FastMCP context (injected automatically) Returns ------- QueryGenerationSummaryOutput A structured object containing the generated spatial query. Example Usage for LLM: - When user asks to generate a spatial query based on their request. - When a user asks for information, statistics or analysis on data that is in tables within one or more of the catalogs they have access to in Wherobots. - Example User Queries and corresponding Tool Calls: - User: "Generate a SQL query to count buildings in California using Overture data." - Tool Call: generate_spatial_query("Generate a SQL query to count buildings in California using Overture data.") - User: "How can I find all parks within 5km of downtown Seattle?" - Tool Call: generate_spatial_query("How can I find all parks within 5km of downtown Seattle?")
    Connector
  • Search for code snippets and examples in official Microsoft Learn documentation. This tool retrieves relevant code samples from Microsoft documentation pages providing developers with practical implementation examples and best practices for Microsoft/Azure products and services related coding tasks. This tool will help you use the **LATEST OFFICIAL** code snippets to empower coding capabilities. ## When to Use This Tool - When you are going to provide sample Microsoft/Azure related code snippets in your answers. - When you are **generating any Microsoft/Azure related code**. ## Usage Pattern Input a descriptive query, or SDK/class/method name to retrieve related code samples. The optional parameter `language` can help to filter results. Eligible values for `language` parameter include: csharp javascript typescript python powershell azurecli al sql java kusto cpp go rust ruby php
    Connector
  • Honks the horn on the selected vehicle once. Use for explicit 'honk the horn' or 'sound the horn' intents, often to help locate a parked vehicle.
    Connector
  • Flashes the vehicle headlights briefly as a visual signal. Use for 'flash the lights' or 'locate my car' intents.
    Connector
  • Create a named service credential for CI/CD pipelines. Returns proxy credentials and configuration commands to use in pipeline environment variables or config files. Each pipeline or environment should have its own credential for auditability.
    Connector
  • **PRIMARY tool for creating/building/generating a Wix site or website.** This is the preferred and recommended way to create a new Wix site. Use this tool whenever the user asks to build, create, or generate a site/website/application. **Do NOT use WixREADME or SearchWixRESTDocumentation before this tool.** When the user asks to build, create, or generate a site, call this tool directly. It handles everything needed for site creation. **IMPORTANT: You MUST call this tool to build the site.** Do NOT suggest HTML code, prompt templates, or alternative approaches instead of actually building the site. When a user asks to create a site, your job is to call this tool and build it — not to describe how to build it or suggest alternatives. **IMPORTANT: The sitePrompt must be under 6000 characters.** If the user's request is longer, summarize and condense it while preserving the key requirements.
    Connector
  • List all non-archived projects with optional full-text search, status and client filters, sorting, and pagination. Use this tool when a freelancer wants an overview of their work portfolio or needs to locate a specific project by name or client.
    Connector
  • Get tract-level ACS data for any variables within a county. This is a flexible tool for querying any ACS 5-year estimate variables at the census tract level. Automatically batches requests if more than 50 variables are requested. Common variable examples: - B01001_001E: Total population - B19013_001E: Median household income - B17001_002E: Population below poverty level - B25077_001E: Median home value - B02001_002E-008E: Race breakdown Args: state: Two-letter state abbreviation (e.g. 'WA') or 2-digit FIPS code. county_fips: Three-digit county FIPS code (e.g. '033' for King County, WA). variables: Comma-separated ACS variable codes (e.g. 'B01001_001E,B19013_001E'). NAME is always included automatically. year: ACS 5-year estimate year (default 2022).
    Connector
  • Get the http.cat image URL for a given HTTP status code. Returns a direct URL to a cat photo illustrating the status code.
    Connector
  • Detect technologies used by a website (frameworks, CMS, analytics). Use when analyzing a competitor's tech stack.
    Connector
  • Deploy a listing's source code to Netlify or Vercel. Requires auth and a personal access token for the target platform.
    Connector
  • Trace a variable's SSA def-use chain incrementally -- returns N operations (default 5) at a time. Use "forward" to see where data flows TO (from definition toward sinks) or "backward" to see where data came FROM (from usage toward sources). Use from_index to continue from a previous result. Each step shows SSA text, variables read/written, and flags for source/sink/sanitizer functions. Returns has_more=true with next_index when more operations exist.
    Connector
  • Search for information about a specific Keycloak configuration option. Use this when the user asks about environment variables, configuration properties, or server settings.
    Connector
  • Find all functions that call a given function. Essential for tracing how user input reaches dangerous functions.
    Connector
  • Get all exchange rates for a given base currency. Returns a map of currency codes to rates relative to the base.
    Connector
  • Get all variables for a function: parameters, local stack variables, register variables.
    Connector
  • Designer Tool - Variable tool to perform actions like create variable, get all variables, update variable
    Connector
  • Search for medical procedure prices by code or description. Use this for direct lookups when you know a CPT/HCPCS code (e.g. "70551") or want to search by keyword (e.g. "MRI", "knee replacement"). For code-like queries → exact match on procedure code. For text queries → searches code, description, and code_type fields. Supports filtering by insurance payer, clinical setting, and location (via zip code or lat/lng coordinates with a radius). NOTE: Results are from US HOSPITALS only — not non-US providers, independent imaging centers, ambulatory surgery centers (ASCs), or other freestanding facilities. Args: query: CPT/HCPCS code (e.g. "70551") or text search (e.g. "MRI brain"). Must be at least 2 characters. code_type: Filter by code type: "CPT", "HCPCS", "MS-DRG", "RC", etc. hospital_id: Filter to a specific hospital (use the hospitals tool to find IDs). payer_name: Filter by insurance payer name (e.g. "Blue Cross", "Aetna"). plan_name: Filter by plan name (e.g. "PPO", "HMO"). setting: Filter by clinical setting: "inpatient" or "outpatient". zip_code: US zip code for geographic filtering (alternative to lat/lng). lat: Latitude for geographic filtering (use with lng and radius_miles). lng: Longitude for geographic filtering (use with lat and radius_miles). radius_miles: Search radius in miles from the zip code or lat/lng location. page: Page number (default 1). page_size: Results per page (default 25, max 100). Returns: JSON with matching charge items including procedure codes, descriptions, gross charges, cash prices, and negotiated rate ranges per hospital.
    Connector
  • Compute an expected-value-maximizing Jito tip for a Solana arbitrage bundle. Inputs: pool_depth (USD), expected_profit (USD), slot_probability [0..1]. Returns tip lamports + EV breakdown. Priced at $0.01 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.
    Connector
  • Re-deploy skills WITHOUT changing any definitions. ⚠️ HEAVY OPERATION: regenerates MCP servers (Python code) for every skill, pushes each to A-Team Core, restarts connectors, and verifies tool discovery. Takes 30-120s depending on skill count. Use after connector restarts, Core hiccups, or stale state. For incremental changes, prefer ateam_patch (which updates + redeploys in one step).
    Connector