Skip to main content
Glama
795,029 tools. Updated 2026-11-17 10:33

"Resources for Product Development" matching MCP tools:

  • Submits an approval request of any supported type: UAT_PROMOTION, UAT_SIGN_OFF, PRODUCTION_PROMOTION, VISIBILITY_CHANGE, OWNERSHIP_TRANSFER, RETIREMENT, DOMAIN_CHANGE, or ROLLBACK. **An agent may submit but never decide**: SpringRoll requires a human approver, and an agent token cannot approve its own request. Confirm with the user before calling this. It creates review work for named people. Type-specific behaviour: • `PRODUCTION_PROMOTION`: this does NOT deploy. It asks. `releaseId` defaults to the application's latest release, and `targetEnvironmentType` to 'production'. Once approved, call springroll.deploy.promote. • `UAT_PROMOTION`: `targetEnvironmentType` is required, 'uat' (or 'development' where Development needs approval). An approval only unlocks the environment it names. • `UAT_SIGN_OFF`: `targetEnvironmentType` defaults to 'uat'. • `ROLLBACK`: `justification` and `targetEnvironmentType` (the environment to roll back) are required. Put the deployment to restore in `payload.targetDeploymentId`; it defaults to the last successful one. • `RETIREMENT`: `justification` is required. • Every other type takes no `targetEnvironmentType`.
    ConnectorNo auth
  • Use this when the user supplies up to 10 exact CardDeals product IDs or brand slugs to compare in one call. Product IDs use the form brand:starbucks. Do not use it for fuzzy discovery; use search_gift_card_deals instead. Unknown IDs are returned in not_found instead of being guessed.
    ConnectorNo auth
  • Fetch the full content for one id returned by `search`: a rental listing (rental:<uuid>), a plan set (plan:<uuid>) or a published page (page:<route>). Returns {id, title, text, url, metadata}. Always cite the url. Hosts that can call specific tools should prefer get_rental or the resources.
    ConnectorNo auth
  • Submits an approval request of any supported type: UAT_PROMOTION, UAT_SIGN_OFF, PRODUCTION_PROMOTION, VISIBILITY_CHANGE, OWNERSHIP_TRANSFER, RETIREMENT, DOMAIN_CHANGE, or ROLLBACK. **An agent may submit but never decide**: SpringRoll requires a human approver, and an agent token cannot approve its own request. Confirm with the user before calling this. It creates review work for named people. Type-specific behaviour: • `PRODUCTION_PROMOTION`: this does NOT deploy. It asks. `releaseId` defaults to the application's latest release, and `targetEnvironmentType` to 'production'. Once approved, call springroll.deploy.promote. • `UAT_PROMOTION`: `targetEnvironmentType` is required, 'uat' (or 'development' where Development needs approval). An approval only unlocks the environment it names. • `UAT_SIGN_OFF`: `targetEnvironmentType` defaults to 'uat'. • `ROLLBACK`: `justification` and `targetEnvironmentType` (the environment to roll back) are required. Put the deployment to restore in `payload.targetDeploymentId`; it defaults to the last successful one. • `RETIREMENT`: `justification` is required. • Every other type takes no `targetEnvironmentType`.
    ConnectorNo auth
  • Retrieve detailed product information for dm-drogeriemarkt products. USE WHEN: ingredients, nutrition facts, allergens, usage instructions, warnings, hazard info, product URLs/images INPUT: DANs (7 digits, preferred) and/or GTINs (8-14 digits) multiple products can be requested at once min 1 / max 50. Use search tool first if only product name is known. OUTPUT: TOON format (compact YAML-like). Fields: name, brand, description, ingredients, nutrition, allergens, usage, warnings, URLs, images. found=false for unresolved IDs. NOT FOR: prices, availability, stock, reviews, recommendations ERRORS: validation error if >50 or no identifiers
    ConnectorNo auth
  • Smart supplier recommendation based on sourcing requirements. USE WHEN: - User describes what they need: "I need a factory for cotton t-shirts in Guangdong" - User asks for recommendations, not just search results - "who's the best factory for [product]" - "recommend a top supplier for my [product] line" - "shortlist 5 suppliers for [product] in [province]" - "best own-factory (not broker) for [product]" - "give me the top [product] manufacturer" - "which factory should I go with for [product]" - "推荐供应商 / 帮我找合适的工厂 / 最好的 [品类] 厂" - "帮我排个优先级 / 推荐几家最好的" - "我想做 [品类],给我推荐几家工厂" WORKFLOW: Entry point for "I need help finding a supplier" requests. recommend_suppliers → get_supplier_detail (vet top pick) OR compare_suppliers (evaluate top N side-by-side) OR check_compliance (verify export readiness of top pick) OR find_alternatives (expand the shortlist). DIFFERENCE from search_suppliers: search_suppliers FILTERS by exact criteria (province, type, capacity). This tool RANKS by fit — prioritizes own-factory, then quality score, then capacity. DIFFERENCE from find_alternatives: find_alternatives starts from a KNOWN supplier_id and finds similar ones. This tool starts from product REQUIREMENTS. RETURNS: { query, total_matches, showing_top, note: "ranking logic", data: [supplier objects] } EXAMPLES: • User: "Recommend me the top 5 factories for sportswear in Fujian" → recommend_suppliers({ product: "sportswear", province: "Fujian", type: "factory", limit: 5 }) • User: "I need the best own-factory (not trading company) for down jackets" → recommend_suppliers({ product: "down jacket", type: "factory", limit: 5 }) • User: "帮我推荐 3 家广东做 T 恤的工厂" → recommend_suppliers({ product: "t-shirt", province: "Guangdong", limit: 3 }) ERRORS & SELF-CORRECTION: • Empty data → try in order: (1) drop province, (2) drop type filter, (3) broaden product (e.g. "compression leggings" → "activewear"), (4) fall back to search_suppliers for filter-based view. • product_type not found in normalizeProductType → use the Chinese term or the parent category. • Rate limit 429 → wait 60 seconds; do not retry immediately. • Empty after 3 retries → tell user: "I don't see verified suppliers matching [product] in [province]. Want me to broaden to nationwide, or try a sibling category?" AVOID: Do not call this when the user wants exact filtering — use search_suppliers. Do not call repeatedly for different limit values — request max once then slice in your response. Do not use for cluster recommendations — use search_clusters. NOTE: Ranking: own_factory > quality_score > declared_capacity_monthly. Source: MRC Data (meacheal.ai). 中文:基于采购需求智能推荐供应商,按 自有工厂 > 质量分 > 产能 排序。
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    Not graded
    maintenance
    Provides a memory server for coding agents over MCP, capturing and retrieving the meaning and rationale behind code decisions down to the function level. It enables agents to search product memory, get task context, and propose new memories to avoid re-deriving or re-breaking past decisions.
    9
    MIT

Matching MCP Connectors

  • Estimate sourcing cost for a product based on fabric price, supplier pricing, and order quantity. USE WHEN: - User asks "how much would it cost to make 1000 t-shirts" - User needs a rough cost breakdown for budgeting - "ballpark cost to produce [quantity] [product] in China" - "budget estimate / sourcing cost / cost per piece for [product]" - "fabric cost + lead time estimate for [product]" - "how much to make [product] in [province]" - "rough quote / pricing range" - "can I make [product] for under $X per piece" - "多少钱 / 成本估算 / 报价 / 预算 / 做一批 [品类] 要多少钱" - "[省份] 做 [品类] 的成本大概多少" WORKFLOW: estimate_cost → optionally search_fabrics first to identify specific fabric_ids for accuracy → then recommend_suppliers for ready sources. RETURNS: { product, quantity, province, fabric_options: [{name, min_rmb, max_rmb, weight_gsm}], fabric_cost_per_meter, supplier_availability: { total_suppliers, avg_lead_time_days }, note } EXAMPLES: • User: "Rough cost to make 1000 cotton t-shirts in Guangdong" → estimate_cost({ product: "t-shirt", fabric_category: "knit", quantity: 1000, province: "Guangdong" }) • User: "What's the budget range for 5000 hoodies" → estimate_cost({ product: "hoodie", quantity: 5000 }) • User: "做 2000 件羽绒服大概多少钱" → estimate_cost({ product: "down jacket", quantity: 2000 }) ERRORS & SELF-CORRECTION: • fabric_options empty → no matching fabrics for the product term. Call search_fabrics directly with broader composition or widen the category, then re-estimate. • supplier_availability.total_suppliers = 0 → drop province filter or broaden product term. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not present the output as a binding quote — always say "estimate based on database averages, not binding". Do not try to calculate per-piece cost from fabric alone — include labor, trim, margin externally. Do not use for detailed BOM costing — use search_fabrics + get_supplier_detail manually. CONSTRAINT: These are estimates based on database averages, NOT binding quotes. Always clarify this to the user. Fabric cost is per meter (typical usage: 1-3m per piece). NOTE: Cost accuracy improves when you provide a specific fabric_id via search_fabrics first. Source: MRC Data (meacheal.ai). 中文:按面料均价 + 供应商供货能力估算 [品类] 的生产成本区间。仅供参考,非正式报价。
    ConnectorNo auth
  • Return the safely validated redirect chain. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Classify MIME type, charset and bounded content length. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Read-only. Returns up to 10 families with status, EOSL window, and page URL. Use this for discovery when you have a name; for an exact part number use lookup_part, and use get_family with a returned slug for the full record.
    ConnectorNo auth
  • Return safe network timing, payload and cacheability diagnostics. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Uninstall a release and remove the resources it created, including volume data. Use it, not delete_resource, for anything install_template created. Provide the release `name`.
    Connector
    Destructive
    OAuth
  • List open times on Upforge's calendar for a free consultation (usually 30 minutes), in the person's own timezone. Call this before book_consultation and let the person pick a time; never pick one for them. Meeting types come live from the scheduler: general-inquiry is the default, and service types such as web-design, application-development or ai-automation route to the right person. Bookings need about a day's notice, so the search starts tomorrow.
    ConnectorNo auth
  • Read dealer buy offers for ONE exact card product, preserving each offer's game, finish, subtype, language, condition, source product, source timestamp, cash and credit fields, quantity and missingFields. Use the catalog product id from spellbook_printings_search. Pokemon offers are English NM/New CoolStuffInc observations when present; no offer or missing field proves a dealer has no stock. This read returns facts and does not choose a vendor or sell cards.
    ConnectorNo auth
  • Returns the Pryx verdict (which product to buy) for one category, once the category's questions are answered. Call it WITHOUT answers to get the questions to ask the user, then call it again with the budget and the answers. Each product carries a productUrl (its pryx.fr page with merchant prices): always show it to the user next to the product you recommend. Read-only. Product names, verdicts and explanations are in French (French market). When nothing separates the finalists, the response says so (tied: true) and elects no winner: do not present any product as the winner in that case.
    ConnectorNo auth
  • Use this when someone wants a teas.co.uk product delivered again and again (subscribe and save). Pass one product id from find_products or a teas.co.uk product link. Returns the subscriber price, how often it comes and a link to the product on teas.co.uk, where the person presses Subscribe and save, then signs in, checks out and pays for the first delivery. This tool orders and charges nothing. Later deliveries follow every cycle as new orders with the same discount, teas.co.uk emails five days before each one and takes no automatic card payments, and the person can pause, resume or cancel at any time (my_subscriptions, change_subscription). When the product cannot be a repeat delivery, eligible is false and note says why.
    ConnectorNo auth
  • Search fashion products on Realry.com. Put only the product itself in `query`, as a short noun phrase ("running shoes", "linen dress", "crossbody bag"), and put gender, price_min/price_max, colors, brand, sale_only/min_discount in their own parameters; use `category` only when the shopper asked for a whole category or the product type is ambiguous. `query` is matched against product text, so sentences and extra words ("for a wedding", "under $100", "cheap", "women's") make it miss. Bad: {"query": "women's black linen summer dress under $100"} Good: {"query": "linen dress", "gender": "women", "colors": "black", "price_max": 100} Good: {"query": "patagonia fleece", "brand": "Patagonia"} Returns product name, price, discount info, seller, and links. Use the Product ID with get_price_comparison to compare prices across all stores. When every store's stock is unconfirmed for 5+ days, those results are listed after fresher ones, so rank is not strict price order under price sorts.
    ConnectorNo auth
  • Change a product of the current workspace: its name, SKU, description, supply type, status, availability, price and currency, the product it nests under, its vendor, or the dates and scope of a dated price row. Use this tool when the user asks to rename a product, change its price, archive it, mark it out of stock, or move it under another product, in any language ("Passe Audit SEO à 1 400 €", "Change SEO audit to 1,400 €"). A new price for a product is always this tool: it never adds an invoice line or drafts an invoice, and it asks for no customer. When the user gives the product_id, call this tool with it directly: the call itself refuses a product that does not exist or that a connected tool synced in, so reading the product first changes nothing. Otherwise find the product_id with well_list_products. REQUIRED: product_id. OPTIONAL (only the fields the user wants changed): hidden, name, sku, description, supply_type, status, availability, stock_tracked, unit_price (a decimal string; it needs a currency), currency, parent_product_id, vendor_company_id, scope_company_id, scope_project_id, product_type_project_id, valid_from, valid_to (YYYY-MM-DD), category_ids (the ordered complete set of existing workspace tag UUIDs; [] clears all tags). Pass null to clear an optional field. Select tags by their UUID; do not infer or create tags from labels or product text. availability here is a manual correction: Well keeps it with who set it and when, and shows it instead of the availability the stock decides. Pass availability: null to remove the correction so the stock decides again. stock_tracked: false makes the product ignore its stock (a service, a product made to order); its own availability then stands. A product a connected tool synced in (synced: true) cannot be changed in Well: the next sync would overwrite the change. The call then fails; tell the user to change it in that tool. hidden: true hides the product from Well's lists and figures and keeps it; hidden: false shows it again. It works on a synced product too, since no sync writes it. When the person asks to delete a synced product, well_delete_product refuses and offers this hide: ask the person, then call this tool with only product_id and hidden: true. For a price request whose unit_price is missing, call this tool with requested_field: "unit_price" and omit unit_price. This request marker opens a follow-up for that field only. It is not sent to the API or stored on the product. Omit requested_field for every other update. Returns { success: true, product } on success, or { success: false, error } on failure.
    Connector
    Destructive
    OAuth
  • How a development project moved through the city — a rezone, subdivision, site plan, conditional-use permit, or apartment/commercial build. Returns the application's lifecycle across meetings (pending → under-review → hearing → approved/denied), oldest first, with the status recorded at each step. WHEN: 'What's the status of the Silo Park development?', 'How did rezone X move through the council?'. WHEN NOT: For issues/policy (not a specific project) use issue_timeline; for quotes use search_meetings. Pass `city` whenever you pass `q`. A project or retailer name often matches applications in several cities, and without a city you will get `application: null` plus a `candidates` list to choose from rather than an answer about the wrong city. Check `candidates` even on a resolved application: one name can cover more than one project in the same city. EXAMPLES: { "q": "Silo Park", "city": "lehi-ut" } — ALWAYS pass city with q { "application_id": "<uuid>" }
    ConnectorAPI key
  • Fetch details only for a Viator product the user selected from find_port_excursions. Returns allowed product content and an affiliate booking URL; no reviews, protected content or live availability. Verify meeting point, return timing and availability on Viator.
    ConnectorNo auth
  • Fetch details only for a Viator product the user selected from find_port_excursions. Returns allowed product content and an affiliate booking URL; no reviews, protected content or live availability. Verify meeting point, return timing and availability on Viator.
    ConnectorNo auth