Skip to main content
Glama
458,064 tools. Updated 2026-08-14 20:18

"MaxScript scripting documentation and tutorials for 3ds Max" matching MCP tools:

  • Get pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getNetworkPools when the user gives numeric constraints or a time window. Use for 'pools over $1M liquidity on Base', 'pools created in the last 24h', or 'high-volume low-liquidity pairs'. Optional filters (AND-combined): volume_24h_min/max, volume_7d_min/max, liquidity_usd_min/max, txns_24h_min, created_after/created_before (Unix timestamps). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort).
    Connector
  • Use to access the Hugging Face Hub. Navigate resources with ls, cat, attach, find, stat, and search over hf:// URIs. Roots: hf://models, hf://datasets, hf://spaces, hf://buckets, hf://collections, hf://papers, hf://docs. For papers, ls hf://papers/ARXIV_ID to discover related resources; cat hf://papers/ARXIV_ID/paper.md or metadata.json. Documentation paths include the current version from each product's llms.txt manifest. Grammar; each token below is one args array element: ls URI [(-R|-r|-lR|-laR|--recursive)] [(-l|-a|-la|-al|--long)] [--glob GLOB] [(-type|--type|--entry-type) TYPE] [--sort SORT] [(-limit|--limit) N] cat URI [RELATIVE_PATH] [(-offset|--offset) N] [(-max-bytes|--max-bytes) N] attach URI [--max-bytes N] stat URI [RELATIVE_PATH] find URI [(-R|-r|--recursive)] [(-name|--name|--glob) GLOB] [(-path|--path) GLOB] [(-type|--type|--entry-type) TYPE] [(-limit|--limit) N] search URI [QUERY...] [(-type|--type|--entry-type) TYPE] [--sort SORT] [--tag TAG] [--kind mcp] [(-limit|--limit) N] TYPE = file|dir|repo|bucket|collection|paper|link. Type aliases: f=file, d=dir, l=link, model|dataset|space=repo. SORT = createdAt|downloads|likes|lastModified|likes30d|trendingScore|mainSize|id|trending|upvotes. URI uses hf://, a typed shorthand such as models/OWNER/REPO, or a canonical https://huggingface.co URL. QUERY and GLOB are each one string token. Search URI: hf://models|datasets|spaces[/OWNER], hf://collections[/OWNER], any hf://docs scope, or exactly hf://papers; not hf://. Repository and collection searches may omit QUERY to browse or filter; documentation and paper searches require it. Search joins multiple positional QUERY tokens with spaces. Cat and stat join one RELATIVE_PATH token to URI. Attach accepts exactly one complete URI and no RELATIVE_PATH or offset. Discover before access: use search, ls, or find to locate targets; use stat when target type is uncertain; then reuse the returned URI, or the Target URI for links, verbatim. Cat reads confirmed UTF-8 text files only. It rejects repositories, directories, model weights, archives, images, media, Parquet, and other binary content. Use stat for metadata instead. Attach returns a complete JPEG, PNG, or WebP repository or bucket file as image content. It classifies only by file extension, never truncates, and has a default and hard limit of 4 MiB; --max-bytes may only lower it. Find recursively matches names and paths within an owner namespace, repository, or supported documentation scope. Use search—not an unscoped find—for global repository, collection, documentation, paper, or Space discovery. Long-list flags are accepted for compatibility; hf_fs listings are already structured, so they do not alter output. Find is already recursive, so recursive flags are accepted without altering behavior. Space search: hf://spaces uses semantic search; repeat --tag to require tags, or use --kind mcp for --tag mcp-server. hf://spaces/OWNER uses owner-scoped keyword search. Documentation: ls hf://docs for products; search any docs scope; use returned hf:// URIs verbatim. Trending listings: ls hf://models/trending, hf://datasets/trending, or hf://spaces/trending. They return up to 20 entries. Trending paths imply trending order; --sort trending|trendingScore is redundant but valid. Trending papers: ls hf://papers/trending. Sort is route-specific: use it with search or supported owner/collection listings, never with repository file listings or documentation. For global trending repositories, use the /trending listing URI. TYPE filters mixed results; omit it when the URI already fixes the result type. Limits and path-specific behavior are documented at hf://README.md. Omit --limit and --sort unless the request asks for a cap, ordering, or exhaustive results. No pipes, redirects, shell expansion, or multiple commands.
    Connector
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    Connector
  • Search ALL JobMojito documentation. This is the single entry point. One call searches both documentation sources in parallel and returns a merged, source-labeled list — you do not need to choose a source or call a separate tool: • "developer" — developer.jobmojito.com: API reference, request/response schemas, tables, webhooks, code examples, integration guides. • "help" — help.jobmojito.com: recruiter, candidate, and administrator product guides (how the platform behaves for end users). Use this whenever you need to understand how a feature, endpoint, field, or workflow works — including before calling an action tool you're unsure about. Then call `get_documentation(url)` with a returned URL to read the full page.
    Connector
  • Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getTopTokens when the user gives numeric constraints or a time window. Use for 'tokens with FDV over $10M on Base', 'newly created tokens today', or 'low-liquidity high-volume tokens'. Optional filters (AND-combined): volume_24h_min/max, liquidity_usd_min/max, fdv_min/max, txns_24h_min, created_after/created_before (Unix timestamps). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort).
    Connector
  • Return a full SukukFi documentation page as markdown. Call search_docs first to find a slug, or pass a known slug such as "for-capital-providers/risk-considerations".
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Analyze stocks and SEC filings to surface key insights, from price and volume to insider activity…

  • MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting.

  • Search Gonka documentation. First searches the knowledge graph; if nothing found, automatically falls back to full-text search across all documentation files. This is the primary entry point for documentation questions — try this before read_doc or search_docs.
    Connector
  • Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge. ## Follow-up Pattern To ensure completeness, use microsoft_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.
    Connector
  • Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    Connector
  • Product overview of Avizo (avizo.ro): compliance-deadline tracking and alerting for Romanian SMEs — what it tracks, alert channels and cadence, post-expiry escalation, integrations, billing model, GDPR posture. Factual summary; use avizo_plans for pricing details and avizo_docs for user documentation.
    Connector
  • Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.
    Connector
  • Hedge-fund share-count history for a ticker. Returns the most recent `limit` snapshots (max 60) plus a summary block (snapshot_count, first/last date and shares). Each row: {date, shares}. Sourced from quarterly 13F filings; lags by up to 45 days. For a snapshot of current sentiment without the timeseries, use get_assets_data and read hedgeFundSentimentData. Args: ticker: Stock ticker (e.g. 'AAPL'). limit: Max snapshots to return (default 60, max 60).
    Connector
  • Query any website's documentation and get cited, multi-page answers in natural language. Use ask_site when you need: (1) answers that synthesize information across multiple pages of a site, (2) documentation from JS-rendered sites (React, Next.js, Vue SPAs) where web_fetch returns empty or partial HTML, (3) citations linking back to the exact source pages, (4) faster results than fetching and reading individual pages one by one. For sites not yet indexed, ask_site auto-crawls and answers in ~60s — no separate submit_site call needed.
    Connector
  • USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.
    Connector
  • USE WHEN reading the full content of a Pine Script v6 documentation file. Returns the file content; when limit is set, a header shows the char range and offset to continue reading. AFTER calling this tool, use offset=<end> to continue if the header indicates more content is available. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md), prefer list_sections() + get_section() instead. Data sourced from bundled Pine Script v6 documentation.
    Connector
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    Connector
  • Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.
    Connector
  • Search across the Honeydew Documentation knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Honeydew Documentation, 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. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).
    Connector
  • Retrieve the complete JSON Schema and metadata for a specific Smart Data Model. Use this when the user already knows the model name and wants its full definition, required fields, attribute types, or documentation URL. Example: get_data_model({"model_name": "WeatherObserved", "include_examples": true})
    Connector
  • List the top-level documentation sections and landing pages from the site's curated index (llms.txt). Use for orientation, then drill in with search_docs or get_doc_page.
    Connector