Skip to main content
Glama
806,701 tools. Updated 2026-11-19 13:44

"YAML" matching MCP tools:

  • Convierte un subconjunto seguro de YAML a JSON; rechaza anclas, alias, etiquetas y varios documentos. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: serializar un valor JSON como YAML (yaml-build). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB. EN: Parses a safe YAML subset (block maps and sequences, plain/quoted scalars, flow [..] {..}, | and > blocks, comments) to JSON. Anchors, aliases, tags, merge keys and multi-documents are rejected. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: serializing a JSON value as YAML (yaml-build). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. [EN completo / full EN: inputSchema.description]
    ConnectorNo auth
  • Serializa un valor JSON como YAML en bloque, con comillas cuando hace falta. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: convertir un subconjunto seguro de YAML a JSON (yaml-parse). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB. EN: Serializes a JSON value as block-style YAML, quoting strings that would otherwise be read as numbers, booleans, null or YAML syntax. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: parsing a safe YAML subset (yaml-parse). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.
    ConnectorNo auth
  • JSON Yaml: Converts a JSON object or JSON string to simplified YAML with two-space indent; arrays render as dash-prefixed lines 🆓 5 free trial calls per signed wallet
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Yaml JSON: Converts simple two-level YAML with scalar, list and nested map values into a JSON object 🆓 5 free trial calls per signed wallet
    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
  • Schema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false, error: <message> } when it fails — feed the error back into your fix and call again until valid. Schema check only; does not save. Use create_config to persist a valid config.
    ConnectorNo auth
  • Schema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false, error: <message> } when it fails — feed the error back into your fix and call again until valid. Schema check only; does not save. Use create_config to persist a valid config.
    ConnectorNo auth
  • Build (or rebuild) the structured index for a knowledge base — the second leg beside vector search. Vector search answers "what does this passage say". It **cannot count, filter numerically or aggregate**, so "how many documents", "which ones are between 1000 and 2000 words", "how many per category" are not answered badly — they are structurally unanswerable. This builds a small per-KB table from whatever structured header the documents share, which the agent can then query with SQL via `query_knowledge_table`. Only worth it when the documents share a machine-readable header (a metadata table, YAML front matter, `Field: value` lines). **Prose gets declined, and that is the right answer** — a table of unique values makes statistics meaningless. `roles` names the fields that must be extracted **exactly** and never paraphrased. Use it when the answer has to quote something the model must not invent: - `identity` — what to call the item (book title, drug name, product name) - `link` — where to send the user - `image` — what to show the user - `code` — the unique identifier Which link is "the" link is a business fact the data does not state — only the customer knows. A declared role that cannot be found comes back in `roles.unresolved` **with candidate field names**: ask the user which one it is, do not guess. **Read `dropped` in the report and tell the user about it.** A column that was thrown out (coverage too low, two columns holding identical values) is invisible in later query results — the model simply works around it — so this report is the only place it is ever mentioned.
    ConnectorNo auth
  • Generate OPC UA NodeSet2.xml and the symbols CSV from a YAML model. Requires an API key (set OPCUA_MODELER_API_KEY env var). NodeIds stay stable only if each regeneration passes back the symbols of the previous one: pass symbols_csv, or mode "new" for a first generation, or mode "renumber" to change ids on purpose. A call with none of these is refused with SYMBOLS_DECISION_REQUIRED. Returns base64-encoded artifacts if the model is valid. The result lists symbol counts (reused/new/dropped), hints and next steps.
    ConnectorNo auth
  • Lints one DESIGN.md file with the official @google/design.md 0.4.0 linter, the same check as `npx @google/design.md lint DESIGN.md`. Best for: checking a DESIGN.md file the user pasted before it goes to a coding agent. Pass the whole file contents in text, including the YAML front matter between the --- lines; a file path or URL will not work, so ask the user to paste the file. Returns: each finding with its severity, rule and token path (broken token references, low text contrast, missing primary color, unused colors, section order, unknown keys), the error, warning and note counts, the sections found and the token counts. The file is valid when it has no errors. Front matter that is not valid YAML comes back as a finding, not an error. Do not use for: comparing two versions (use diff_design_md) or reading a website (use extract_design_md).
    ConnectorNo auth
  • MANDATORY: Call score in every interaction turn that uses search or batch_search. ## When to submit An interaction turn starts with a user request and ends when you send your final response for that request. It may include multiple tool calls. Track pending search feedback within this turn; do not wait for a later user message to submit it. Submit at BOTH of these checkpoints whenever they apply: 1. During the turn: as soon as 10 successful searches are pending, call score for those 10 before starting another search. If completed batch or parallel calls leave more than 10 pending, submit batches of 10 until fewer than 10 remain, then continue your work. 2. At the end of the turn's searching: submit all remaining pending feedback before sending your final response, even if only one search is pending or you could not fully answer the user. Do not wait to reach 10. Count one successful search call as one search, and each successful batch_search sub-query as one search. Each needs its own request_id and score. Successful searches with empty results count too; failed searches and extract calls do not. If you search again after submitting feedback, collect the new results and apply the same checkpoints. Examples: - 3 searches in a turn: submit 3 entries when searching ends, before your final response. - 10 searches in a turn: submit 10 immediately; if no further searches occur, no additional submission is needed. - 12 searches in a turn: submit 10 at the threshold, then the remaining 2 when searching ends. Each call must contain 1-10 entries. Never send an empty batch. Do not resubmit request_ids already queued. If no eligible searches are pending, no submission is needed. Do not skip feedback because the results were good: a perfect result still needs score 5. Never invent an ID when neither the result's YAML block nor its metadata provides one. Feedback is free and never consumes quota or credits. A queued response acknowledges receipt, not database persistence. ## Fields - request_id: Copy from the YAML block at the end of each successful search result, including each batch_search sub-query. The same IDs remain available in metadata (_meta.request_id for search, the corresponding entry of _meta.request_ids for batch_search). Never invent it. - score: Integer 1-5, judged against the criteria below. Score each search or sub-query separately. ## Scoring criteria (use the FIRST level that matches) 5 - Fully answered. The results directly support a complete answer; no extra extract or follow-up search is needed. 4 - Mostly answered. Minor gaps remain, but they do not block the answer. 3 - Partially answered. You still need another search or an extract call to answer well; coverage is incomplete but some results are usable. 2 - Largely insufficient. Most results are irrelevant, outdated, or too shallow; only a small part is usable. 1 - Not useful at all. Results are off-topic, empty, or have nothing to do with the query. Judge the results against the user's actual information need, not against how confident the snippets sound. A partial answer with unrelated extras is 3, not 4.
    ConnectorNo auth
  • ALWAYS CALL THIS FIRST, before any other komuta tool. Classify the user's request into exactly one intent and pass it here. Returns the workflow contract: a FIXED ordered step list (never skip, reorder, or invent steps) and the EXACT tool set allowed for the task — no other komuta tool may be called while this workflow is active. Call again with a new intent when the user's request changes. Intents: MANAGE_JOBS — Run, cancel, suspend or resume existing Jobs/CronJobs, or inspect their configuration and history. New job creation uses DEPLOY_STACK. | MANAGE_SERVICE_RUNTIME — Inspect service configuration, ports, health probes, routing, dependencies; change fixed replicas, sleep/wake, automatic sleep (turn idle sleep on or off), maintenance mode (turn it on or off, change the visitors' maintenance message) or control a rollout. Also the organization's monthly free awake hours and a free-plan service's keep awake (always on) add-on: its status, price, purchase or turning it off. | ACCOUNT_BILLING — Account-wide costs, statements, build allowance, wallet, payment links, approved wallet payments, the Doktor AI add-on subscription and asking Komuta for a white-label report or evidence pack pilot. | MANAGE_ALERTS — Inspect alert rules, templates, notification channels and history; deploy, undeploy or enable/disable existing rules and channels; create an email notification channel or send a test notification through a channel. Also scheduled Service Doctor health reports: list, create, change, pause, delete or preview when and where they are sent, or send one right away. | SECURITY_AUDIT — Inspect security audit history and evidence for an organization or service. | MANAGE_ADDON_LIFECYCLE — Manage an existing Postgres, Valkey or RabbitMQ instance: backup, restore, restart, plan change, suspension, deletion scheduling or credential rotation. | MANAGE_API_GATEWAYS — Create, inspect and manage API gateways end to end: settings, connected APIs, endpoints and their policies (cache, limits, authentication, header and path rewrites, request checks), callers' keys and usage plans, OpenAPI import, test requests, configuration history, export/import, applying changes, scaling, bandwidth and version. | PLATFORM_ADMIN — Platform administrator: inspect cross-tenant services, platform capacity, addons, tenant status and platform health; manage tenant suspension, limits and maintenance. | ADMIN_TENANT_BILLING — Platform administrator: inspect or change another tenant's billing, spending limit, wallet balance or statements. | ADMIN_BACKGROUND_JOBS — Platform administrator: inspect workers and background/recurring jobs, retry jobs or delete failed work. | DEPLOY_STACK — ANY request to publish/provision/deploy a new app, Git repository, Service, Job or CronJob goes directly to this workflow, even when the user never says Stack or YAML and even for a single service. Also use it to create/use komuta.yaml, deploy multiple services/addons/domains together, validate/plan/apply a Stack, resume a Stack run, inspect Stack drift, or export an applied Stack. Only a redeploy of a workload that already exists on Komuta remains REDEPLOY_SERVICE. | REDEPLOY_SERVICE — User wants to redeploy a workload that already exists on Komuta: deploy a new version, re-run/re-trigger its pipeline, or change the branch it deploys from. NOT for publishing a brand-new workload (use DEPLOY_STACK). | MANAGE_AUTOSCALING — User wants to see, enable, disable, or change a service's autoscaling / HPA: min or max replicas, target CPU %, target memory %, or the scale-up/scale-down stabilization windows. | MANAGE_AUTO_DEPLOY — User wants to see, enable, disable, or change a service's auto-deploy / deploy-on-push behavior: turn it on or off, include/exclude path patterns, the cooldown between triggers, or commit-message skip directives. NOT for manually redeploying right now (use REDEPLOY_SERVICE). | MANAGE_ENV_VARS — User wants to see, add, or change environment variables / runtime configuration / secrets of an existing service — including wiring a managed addon's connection string into a service, copying stored secrets from another service, or importing an environment group's variables into a service. NOT for creating, filling or pushing environment groups themselves (MANAGE_ENV_GROUPS), for creating the addon itself (ADDONS) or for a first deployment (DEPLOY_STACK handles initial configuration and secret handoff). | MANAGE_ENV_GROUPS — User wants to see, create or fill an environment group (a shared set of variables used by several services), see which services use it or have fallen behind it, or push its current values to those services. NOT for one service's own variables or importing a group into one service (MANAGE_ENV_VARS). | MANAGE_DOMAINS — User wants to add/bind a custom domain (their own hostname) to an existing service, check its DNS/TLS verification status, re-check after they've updated DNS records, or remove a domain. NOT the auto-generated *.komuta.app hostname shown by komuta_get_service_overview — that one isn't managed here. A domain requested as part of a first deployment belongs in DEPLOY_STACK. | MANAGE_STORAGE — User wants to see, attach, resize/upgrade/downgrade the plan of, or remove a persistent storage volume (disk/PVC) mounted into a service's container. NOT a managed database/cache/queue's own storage (that's ADDONS) and NOT compute sizing (that's MANAGE_AUTOSCALING). | MANAGE_ACCESS_PROTECTION — User wants to see or change who may open an existing service from the internet: turning access protection on or off, allowed IP addresses, requiring Komuta sign-in, path rules (blocked pages, webhook paths open without sign-in, pages for chosen people only), an expiry, telling the application who signed in and how to verify it, sharing the service with members, the organization, linked organizations, people by e-mail, everyone at a domain or everyone who signs in with the organization's identity provider (optionally some of its groups), the organization's identity providers for visitors, service tokens for machines, which other services may reach it over the private network, the access log of sign-ins, page views and refusals, whether a particular person, visitor or machine can open a given page and why, or the organization-wide setting for sharing outside the organization. | ADDONS — User wants a database, message queue, or cache — create one, list them, or get connection info. | STATUS_OVERVIEW — User asks what they have running, whether a service is comprehensively healthy or at risk, the state of a service or addon, a general account overview, wants to see/search a service's logs or request traces (failing/slow endpoints), or asks about a service's billing — current charges, cost so far, or its invoice history. | MANAGE_RECOMMENDATIONS — User accepts, defers or dismisses a critical recommendation Komuta returned for a service, wants its action plan prepared, approved, marked as done, or verified, or asks Komuta to fix a Service Doctor finding itself (one-click fix), or wants a Service Doctor README badge turned on, renewed or turned off. NOT for asking whether a service is healthy (STATUS_OVERVIEW). | GENERAL_CHAT — No platform action requested — questions, chit-chat, or explanations. Includes 'what is Komuta?', 'what can it do?', how deploys/addons/pricing work conceptually, and 'how do I get started / get an API key?'. Returns: { workflow, title, steps, allowedTools, recovery, rules }. Show user: nothing verbatim — steps/allowedTools/rules are agent-facing orchestration instructions; act on them and speak to the user in your own words. Never show user: the raw steps/allowedTools/recovery/rules payload — never dump the workflow contract into the chat. Sends: nothing to the backend — only switches this session's active workflow (overwriting the previous one's context).
    Connector
    Destructive
    OAuth