"Grafana" matching MCP tools:

• zaira_get_toolA

  Zaira Labs GuideA

  Get full details for a specific developer tool by its slug. The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields. Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call. If the slug is not found, returns an error with similar-slug suggestions. Examples: - Postgres core engine: {slug: "postgresql"} - Stripe (single entry, no -cloud/-oss split): {slug: "stripe"} - Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"} - Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"} - GitHub's MCP server: {slug: "github-mcp"} Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` for the managed lane, `{base}-oss` for the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only. - Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js"). - Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase. Risk: read-only, closed-world, idempotent — no state change possible.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize IntelligenceB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize GovernanceB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize HealthcareB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize Real EstateB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize Crypto & DeFiB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize FinanceB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• get_saas_negotiation_playbookA

  Stratalize OracleB

  Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

  ConnectorNo auth

• taifoon_explorer_jobsA

  Taifoon coordination layerC

  Every job that went through the Taifoon coordination layer (GET /v1/explorer/jobs): auto-match and catalog demands, broker hires and jobs on our assurance hooks on Base and the devnet. Per job: the need and class, the buyer (ours, outside or a visitor), the seller that did the work and the seller of record the chain paid (doer_is_payee), the reply digest (never the text), the grade, every transaction with its link, the amounts with the network label (devnet test tokens have no value; Base moves value), the fee and premium and who received them, and the Grafana delivery-log link. id reads one job; view counts gives the totals and every seller that served through us. Free, read-only.

  ConnectorNo auth

• query_logs

  Ankra

  Search the cluster's registered log store (Grafana Loki, Elasticsearch, OpenSearch, or VictoriaLogs - configured in Cluster Settings > Data Sources > Log Source) over a time window: historical, aggregated logs across pods and restarts, unlike get_pod_logs which streams one live pod. Use structured filters (namespaces/pods/containers plus a text search) or raw_query for a provider expression (LogQL on Loki, a JSON query-DSL clause on Elasticsearch/OpenSearch, LogsQL on VictoriaLogs). Results are normalized {timestamp, line, labels, fields} entries, newest first by default, truncated to the limit. Every result carries cluster_attribution, because one log store can be shared by several clusters (the Ankra platform clusters ship their platform namespace into the same OpenSearch indices with identical pod names): when the store attributes lines to clusters (a `cluster` field on Elasticsearch/OpenSearch, a `cluster` stream label on Loki, stamped by the shipper) the query is scoped to this cluster's value, and lines attributed to other clusters or carrying no attribution are excluded and counted (other_clusters_hits, unattributed_hits; absent when the store cannot count them). cluster_attribution.state is "attributed" (scoped; this cluster's lines exist in the window), "requested_absent" (the store attributes other clusters' lines but none in the window carries this cluster's value - the result is empty and nothing in the store can be attributed to this cluster; report that, never substitute unattributed lines), or "none" (no line in the window carries the field; the result is NOT scoped and, if the store is shared, may include other clusters' lines - say so). Relay the note. On a scoped Loki store raw_query is refused; use the structured filters, which are scoped automatically. On Elasticsearch/OpenSearch each entry's fields object carries the requested extra _source paths (default: level and extra, the platform's structured-attribute container - cluster_id, error, etc.); pass fields to pick different paths. Attributes indexed as flat_object match on exact full leaf values only, via dotted paths in raw_query (e.g. {"match": {"extra.cluster_id": "<uuid>"}}) - substring search inside attribute values is not supported by the store. total_hits_relation says how to read total_hits: "eq" means it is the exact number of matches, "gte" means the store stopped counting (Elasticsearch and OpenSearch cap at index.max_result_window, 10,000 by default) and total_hits is only a floor - in that case say "at least N", never state it as the exact count. Use this for 'what errored around 14:00', cross-pod correlation, and logs from restarted/deleted pods. Read-only.

  ConnectorOAuth

• create_alertmanager_silence

  Ankra

  Create a silence in the cluster's Prometheus Alertmanager so matching alerts stop notifying (Slack, email, ...) until the silence ends. Matchers come from the alert's own labels - always anchor on an exact alertname matcher (e.g. alertname=KubeVersionMismatch) and add narrowing labels like cluster or namespace when known; at least one exact (non-regex) matcher is required. Duration accepts '30m', '2h', '24h', '14d', '2w' (default 2h, maximum 30d - longer suppressions need a human in Alertmanager/Grafana). A comment is required: it is the operator-visible reason shown next to the silence. The silence starts immediately (backdated one minute so it never sits pending) and the response carries the silence id - relay it so the silence can be expired early with expire_alertmanager_silence. The Alertmanager service is auto-discovered; pass namespace/service/port only for non-standard installs.

  ConnectorOAuth

• get_mcp_catalog

  Ankra

  List the curated MCP integration catalog: the external tool vendors (OneUptime, Sentry, PostHog, GitHub, Grafana, ...) an organisation admin can connect as MCP tool servers with a guided setup. Each adapter carries the vendor's endpoint placeholder, the credential header it needs (with the exact value form, e.g. 'Bearer <token>'), the platform-pinned read-tool patterns, and the recommended starting tool set. Call this before register_mcp_server to pick the right adapter_key, or to answer what integrations Ankra supports out of the box. Custom servers (any MCP endpoint over http/sse) are registered without an adapter_key. Read-only.

  ConnectorOAuth