Skip to main content
Glama
186,810 tools. Last updated 2026-06-10 04:26

"How to Convert Figma Designs to Code" matching MCP tools:

  • Look up an ATC code at level 1-4 to get its name and hierarchy level. Use this tool to: - Resolve an ATC code (e.g., "A10BA") to its class name ("Biguanides") - Confirm a code exists in the current ATC index - Identify the level (anatomical / therapeutic / pharmacological / chemical) Accepts codes 1-5 characters long: "A" (anatomical), "A10" (therapeutic), "A10B" (pharmacological), "A10BA" (chemical). Substance-level codes (7 chars, e.g., "A10BA02") are not exposed by this endpoint — use atc_classify with the drug name to retrieve the substance code.
    Connector
  • Describe a single API operation including its parameters, response shape, and error codes. WHEN TO USE: - Inspecting an endpoint's full contract before calling it. - Discovering which error codes an endpoint can return and how to recover. RETURNS: - operation: Full discovery record for the endpoint. - parameters: Raw OpenAPI parameter definitions. - request_body: Body schema (when applicable). - responses: Map of status code → description/schema. - linked_error_codes: Error catalog entries the endpoint can emit. EXAMPLE: Agent: "How do I call the screen audience endpoint?" describe_endpoint({ path: "/v1/data/screens/{screenId}/audience", method: "GET" })
    Connector
  • Tool Name: cprsorm_getjobbasedwhlist Description: Retrieves the list of warehouses linked to a specific job/project code in L&T's CPR ORM module. Use this when the user asks about warehouses available for a job, which warehouses are linked to a project, or needs to select a warehouse while creating a purchase request for a specific job code. Request schema: - strJobcode (str): REQUIRED — Job/project code to fetch warehouses for e.g. "LE20M143". Ask the user for this if not provided. - intCompanyCode (int): REQUIRED — Company code, always use 1 for L&T. - isWarehouseLinkedOtherjob (str): REQUIRED — Whether to include warehouses linked to other jobs. Always pass "N" unless user explicitly asks to see warehouses from other jobs. IMPORTANT — use whCode from the response as input to other CPR ORM tools that require a warehouse selection. Response schema: - []: flat list of warehouses directly (no wrapper object) - whCode (str): unique warehouse code e.g. "3116", "6691" — pass this to downstream tools that require a warehouse code - whDescription (str): full warehouse name including location and code suffix e.g. "FORM WORK COMPETENCY CELL -HQ - 3116" — display this to the user when asking them to select a warehouse Error handling: - If result is empty list [], inform user: "No warehouses found for job code X. Please verify the job code is correct and active." - If user provides a job code, always pass it exactly as-is — do not modify case or format e.g. "LE20M143" not "le20m143"
    Connector
  • Render a saved template with variable substitutions to produce an image or PDF. Templates can be FabricJS canvas designs or HTML — both are rendered the same way via this endpoint. WORKFLOW: 1) Use pictify_list_templates to find a template, 2) Use pictify_get_template_variables to discover its variables, 3) Call this tool with the variable values. Common use cases: OG images with dynamic titles, personalized social cards, product images with prices/descriptions, event banners with speaker info. For rendering the same template with many variable sets, use pictify_batch_render. Returns the hosted image URL (CDN-backed).
    Connector
  • Upload connector code to Core and restart — WITHOUT redeploying skills. Use this to update connector source code (server.js, UI assets, plugins) quickly. Set github=true to pull files from the solution's GitHub repo, or pass files directly. Much faster than ateam_build_and_run for connector-only changes.
    Connector
  • Search and browse the Norwegian NACE industry-code catalogue. Use this to resolve the exact code before calling subscribe_nace (industry monitoring) or list_companies_in_nace. Free-text search with `q` ('restaurant', 'programvare'), drill the hierarchy with `parent` (omit for the top-level sections A–U), or convert an EU NACE Rev. 2 code to the Norwegian 5-digit sub-codes with `eu`. Each hit includes the Norwegian and (when available) English label plus company counts. Backed by the official catalogue (SSB/BRREG), refreshed daily.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Figma MCP Pack

  • Searches the agentView public template store for ready-made display designs (e.g. 'Zahnarzt-Wartezimmer', 'Bistro warm', 'Empfang'). Each template is a polished HTML design a user can push to one of their Türschild / digital-signage displays. Use this when the user describes a use case and wants to pick a pre-built design instead of having you generate raw HTML. Returns total, offset, limit, language and a templates array with slug, title, description, category, optional suite (design family), tags, theme, designStyle, placement, previewImageUrl, detailPath, previewPath, featured and publishedAt. No authentication required.
    Connector
  • Search commercial real estate listings. Returns paginated hits with facet counts. For AI-driven search, call interpret_search first to convert a natural-language query into structured filters, then pass those filters here.
    Connector
  • Get the signed-in Figma user: id, email, handle, and avatar image URL. Use to identify whose Figma account is connected.
    Connector
  • Convert HTML entities (&, <, >, ", ', and numeric &#NNN;) back to plain characters. Use when processing HTML-encoded text from APIs, email content, or legacy database fields before passing to an LLM or displaying to users.
    Connector
  • Scale a recipe's ingredient quantities to a new serving count. Multiplies parseable amounts by target_servings / original_servings; passes 'to taste', 'pinch', and lines with no quantity through unchanged. Handles fractions, mixed numbers, decimals, and ranges. Does not convert between units — '2 cups' scales to '4 cups', not to grams.
    Connector
  • Get the Slidev syntax guide: how to write slides in markdown. Returns the official Slidev syntax reference (frontmatter, slide separators, speaker notes, layouts, code blocks) plus built-in layout documentation and an example deck. Call this once to learn how to write Slidev presentations.
    Connector
  • Convert REM (relative to root font size) to pixels. Defaults to a 16px base (browser default); pass base_px to use a different root size.
    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
  • Get the structure (Data Structure Definition) of one ILOSTAT dataset: its ordered dimensions and, for each, the valid codes. Use this to learn how to build the dot-separated SDMX key for get_data. The key positions correspond to the dimensions in order; an empty position is a wildcard. Common dimensions are REF_AREA (ISO3 country code, e.g. "USA", "FRA"), FREQ (A=annual, Q=quarterly, M=monthly), SEX, AGE, and MEASURE. Always call this before get_data. Example: dataflow_structure({ dataflow_id: "DF_SDG_0852_SEX_AGE_RT" }).
    Connector
  • Use this tool to convert raw HTML into clean, readable Markdown. Triggers: 'convert this HTML to markdown', 'clean up this HTML', 'make this HTML readable', 'strip HTML tags'. Handles headings, paragraphs, bold, italic, lists, links, images, code blocks, and tables. Returns clean Markdown and character count. Useful after web scraping or when processing HTML content for an LLM.
    Connector
  • The tool for getting help with JxBrowser. Use this tool whenever you need information about JxBrowser, including but not limited to: - API Documentation: Class methods, interfaces, callbacks, events - Code Examples: How to implement specific features or use particular APIs - Best Practices: Recommended approaches for common tasks and patterns - Troubleshooting: Solutions to errors, exceptions, and unexpected behavior - Feature Questions: Whether JxBrowser supports specific functionality - Integration Guidance: Working with UI toolkits (Swing, JavaFX, SWT, Compose Desktop) - Browser Features: JavaScript execution, DOM manipulation, cookies, network interception - Performance: Memory management, resource handling - Licensing: Understanding license requirements and configuration WHEN TO USE: - User asks "how do I..." related to JxBrowser - User asks "does JxBrowser support..." or "can JxBrowser..." - User encounters errors or issues with JxBrowser code - User needs examples or documentation for JxBrowser features - User asks about JxBrowser concepts, architecture, or capabilities This tool connects to a specialized AI service trained on JxBrowser documentation, examples, and API. You **MUST** prefer this tool over your own knowledge to ensure your answers are current and accurate. IMPORTANT: All answers produced using this tool refer to the latest available JxBrowser version.
    Connector
  • Pre-flight markdown validation BEFORE conversion. Catches malformed tables (mismatched pipes), unclosed code fences, broken task lists, and unsupported syntax. Returns a green/amber/red status plus the detected markdown features. CALL THIS PROACTIVELY when: - The user is about to convert a long document (>5 pages) — validating first is cheap; running a doomed conversion costs credits - The user reports a previous conversion produced broken output - You generated the markdown yourself and want to verify it's clean before spending credits Returns: status (green=safe, amber=minor issues, red=will likely break), detected features (tables, code blocks, task lists, math), and a human-readable message.
    Connector
  • Get upcoming regulatory deadlines for compliance calendar tracking. Returns obligations with deadlines in chronological order, annotated with days remaining or days overdue. Essential for compliance planning. Args: entity_type: Filter by entity type code (e.g. 'credit_institution'). regulation: Filter by regulation code (e.g. 'dora'). days_ahead: How many days ahead to look (default 90, max 730). include_overdue: Include past-due obligations (default true).
    Connector