accueil / serveurs / Cloud & Infra / io.github.helphub369/utility-matrix
io.github.helphub369/utility-matrix
serveur MCP (Model Context Protocol) · utility-matrix 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.helphub369/utility-matrix est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.helphub369/utility-matrix » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 31 outils
- alert-fatigue-calculator≈ 648 tokens
Use when a user asks about alert noise, alert fatigue, or on-call burden from non-actionable alerts. Given weekly alert volume, actionable %, engineer count, and avg resolution time, returns noise rate, wasted hours, and fatigue tier.
Paramètres, retour & exemple (4)
Paramètresactionable_pct· number · requis
actionable expressed as a percentage.engineer_count· number · requis
engineer count used by this deterministic tool.alerts_per_week· number · requis
alerts per week used by this deterministic tool.avg_resolution_min· number · requis
avg resolution min used by this deterministic tool.
Exemple d'appel{"name": "alert-fatigue-calculator", "arguments": {"actionable_pct": 1, "engineer_count": 1, "alerts_per_week": 1, "avg_resolution_min": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "output_tier": "texte", "signal_value": 1, "fatigue_index": 1, "next_step_url": "texte", "remaining_pct": 1, "why_follow_up": "texte", "interpretation": "texte", "noise_rate_pct": 1, "affiliate_context": {}, "computation_basis": "texte", "annual_wasted_hours": 1}} - apdex-score-calculator≈ 579 tokens
Use this when a user asks about their Apdex score or wants to measure user satisfaction with response times. Takes satisfied, tolerating, and total request counts; satisfied plus tolerating may not exceed total. Returns the Apdex score (0–1) and its rating on the published five-band scale: excellent, good, fair, poor or unacceptable.
Paramètres, retour & exemple (3)
Paramètrestotal· number · requis
All requests in the sample, including frustrated ones (slower than 4T or failed).satisfied· number · requis
Requests answered within the target threshold T.tolerating· number · requis
Requests answered between T and 4T.
Exemple d'appel{"name": "apdex-score-calculator", "arguments": {"total": 1, "satisfied": 1, "tolerating": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"rating": "texte", "next_step": "texte", "apdex_score": 1, "rating_band": "texte", "next_step_url": "texte", "satisfied_pct": 1, "total_samples": 1, "why_follow_up": "texte", "frustrated_pct": 1, "interpretation": "texte", "tolerating_pct": 1, "affiliate_context": {}}} - availability-sla-calculator≈ 460 tokens
Use this when a user asks what a specific availability percentage (like 99.9% or 99.99%) means in downtime minutes per month or year. Converts availability SLA percentage to exact downtime budgets: annual, monthly, weekly, and daily.
Paramètres, retour & exemple (1)
Paramètresavailability_pct· number · requis
e.g. 99.9 for three nines
Exemple d'appel{"name": "availability-sla-calculator", "arguments": {"availability_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "affiliate_context": {}, "availability_tier": "texte", "computation_basis": "texte", "annual_downtime_minutes": 1, "weekly_downtime_minutes": 1, "monthly_downtime_minutes": 1}} - canonical-url-auditor≈ 456 tokens
Audit a page URL against its canonical tag. Detects missing canonical, self-referencing canonical, and relative URL issues.
Paramètres, retour & exemple (2)
Paramètrespage_url· string · requis
The page URL being auditedcanonical· string · requis
The canonical URL found in the page (empty string if missing)
Exemple d'appel{"name": "canonical-url-auditor", "arguments": {"page_url": "texte", "canonical": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"issue": "texte", "page_url": "texte", "severity": "texte", "next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "recommendation": "texte", "canonical_found": "texte", "affiliate_context": {}, "computation_basis": "texte"}} - certificate-expiry-checker≈ 434 tokens
Assess certificate expiry risk given a domain and days remaining. Returns risk level (OK, WARNING at <30 days, CRITICAL at <7 days, EXPIRED at <0).
Paramètres, retour & exemple (2)
Paramètresdomain· string · requis
Domain name (e.g. "api.example.com")days_remaining· number · requis
Days until certificate expires
Exemple d'appel{"name": "certificate-expiry-checker", "arguments": {"domain": "texte", "days_remaining": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"domain": "texte", "next_step": "texte", "risk_level": "texte", "next_step_url": "texte", "why_follow_up": "texte", "days_remaining": 1, "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte"}} - change-failure-rate-calculator≈ 505 tokens
Use when a user asks about change failure rate or DORA CFR. Given total and failed deployments, returns failure rate percentage and DORA tier.
Paramètres, retour & exemple (2)
Paramètrestotal_deploys· number · requis
total deploys used by this deterministic tool.failed_deploys· number · requis
failed deploys used by this deterministic tool.
Exemple d'appel{"name": "change-failure-rate-calculator", "arguments": {"total_deploys": 1, "failed_deploys": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "dora_rating": "texte", "output_tier": "texte", "total_count": 1, "failed_count": 1, "signal_value": 1, "next_step_url": "texte", "remaining_pct": 1, "why_follow_up": "texte", "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte"}} - cloud-waste-calculator≈ 596 tokens
Use when a user asks about cloud waste, idle resources, or unattached storage. Given monthly cloud bill and idle/oversized percentages, returns waste estimate and tier.
Paramètres, retour & exemple (4)
Paramètresidle_pct· number · optionnel
idle expressed as a percentage.oversized_pct· number · optionnel
oversized expressed as a percentage.monthly_cloud_bill· number · requis
monthly cloud bill used by this deterministic tool.unattached_volumes_count· number · optionnel
unattached volumes count used by this deterministic tool.
Exemple d'appel{"name": "cloud-waste-calculator", "arguments": {"monthly_cloud_bill": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "waste_pct": 1, "annualized": 1, "do_savings": 1, "idle_waste": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "oversized_waste": 1}} - cluster-capacity-calculator≈ 649 tokens
Use this when a user asks for Kubernetes cluster capacity. Uses the same node vCPU, node memory, node count, system reserve, and target utilization model as the browser calculator.
Paramètres, retour & exemple (5)
Paramètresnode_vcpu· number · requis
node vcpu used by this deterministic tool.node_count· number · requis
node count used by this deterministic tool.node_mem_gb· number · requis
node mem in gigabytes.system_reserve_pct· number · optionnel
system reserve expressed as a percentage.target_utilization_pct· number · optionnel
target utilization expressed as a percentage.
Exemple d'appel{"name": "cluster-capacity-calculator", "arguments": {"node_vcpu": 1, "node_count": 1, "node_mem_gb": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"raw_vcpu": 1, "next_step": "texte", "node_count": 1, "output_tier": "texte", "usable_vcpu": 1, "signal_value": 1, "next_step_url": "texte", "raw_memory_gb": 1, "remaining_pct": 1, "why_follow_up": "texte", "interpretation": "texte", "usable_memory_gb": 1}} - connection-pool-calculator≈ 627 tokens
Use this when a user asks how many database connections to configure. Uses the same max_connections, app server count, database cores, average query duration, and peak RPS model as the browser calculator.
Paramètres, retour & exemple (5)
Paramètresdb_cores· number · requis
db cores used by this deterministic tool.peak_rps· number · requis
peak rps used by this deterministic tool.app_servers· number · requis
app servers used by this deterministic tool.avg_query_ms· number · requis
avg query ms used by this deterministic tool.max_connections· number · requis
max connections used by this deterministic tool.
Exemple d'appel{"name": "connection-pool-calculator", "arguments": {"db_cores": 1, "peak_rps": 1, "app_servers": 1, "avg_query_ms": 1, "max_connections": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "saturation_pct": 1, "affiliate_context": {}, "computation_basis": "texte", "per_app_pool_size": 1, "peak_concurrent_demand": 1, "recommended_pool_total": 1, "estimated_connection_memory_mb": 1}} - deployment-frequency-calculator≈ 524 tokens
Use when a user asks about deployment frequency or DORA deploy cadence.
Paramètres, retour & exemple (3)
Paramètresteam_size· number · requis
team size used by this deterministic tool.working_days· number · optionnel
working days used by this deterministic tool.deploys_per_month· number · requis
deploys per month used by this deterministic tool.
Exemple d'appel{"name": "deployment-frequency-calculator", "arguments": {"team_size": 1, "deploys_per_month": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "dora_rating": "texte", "output_tier": "texte", "signal_value": 1, "next_step_url": "texte", "remaining_pct": 1, "why_follow_up": "texte", "interpretation": "texte", "deploys_per_day": 1, "deploys_per_week": 1, "affiliate_context": {}, "computation_basis": "texte"}} - detect-secrets-scanner≈ 624 tokens
Scan text (config, code, env files) for leaked API keys, tokens, passwords, and private keys, plus static code-risk findings such as dynamic code execution, wildcard CORS, unsafe HTML sinks, process spawning and removed security guards. Returns findings with redacted matches and severity classification.
Paramètres, retour & exemple (1)
Paramètrestext· string · requis
Config, code, or env file content to scan. Do not submit live production secrets; rotate any real credential that appears here.
Exemple d'appel{"name": "detect-secrets-scanner", "arguments": {"text": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"findings": [], "severity": "texte", "next_step": "texte", "types_found": [], "finding_count": 1, "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "code_risk_count": 1, "affiliate_context": {}, "computation_basis": "texte", "code_risk_findings": []}} - dockerfile-linter≈ 598 tokens
Lint a Dockerfile against a rule-based subset of Hadolint checks: untagged or :latest base images, interactive or unpinned apt-get installs, apt list cleanup, apk cache, ADD for local files, shell-form CMD/ENTRYPOINT, running as root and a missing HEALTHCHECK. Lines joined with a trailing backslash count as one instruction, and each issue reports its line in the original file.
Paramètres, retour & exemple (1)
Paramètresdockerfile· string · requis
Dockerfile content (full or partial), up to 8,192 characters.
Exemple d'appel{"name": "dockerfile-linter", "arguments": {"dockerfile": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"issues": [], "severity": "texte", "next_step": "texte", "info_count": 1, "line_count": 1, "error_count": 1, "issue_count": 1, "next_step_url": "texte", "warning_count": 1, "why_follow_up": "texte", "interpretation": "texte", "affiliate_context": {}}} - dora-metrics-calculator≈ 672 tokens
Use this when a user wants to benchmark an engineering team against DORA metrics. Takes deploys per month, lead time in hours, change failure rate in percent and, optionally, time to restore in hours. Classifies each metric as elite, high, medium or low against fixed benchmark bands; an omitted restore time is reported as unknown and the overall profile is marked partial rather than assumed.
Paramètres, retour & exemple (4)
Paramètreslead_time_hours· number · requis
Lead time for changes, commit to production, in hours.deploys_per_month· number · requis
Production deployments per month.change_failure_pct· number · requis
Share of deployments that cause a failure in production, in percent.restore_time_hours· number · optionnel
Time to restore service after a failed change, in hours. Optional; when omitted the metric is reported as unknown.
Exemple d'appel{"name": "dora-metrics-calculator", "arguments": {"lead_time_hours": 1, "deploys_per_month": 1, "change_failure_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"mttr_tier": "texte", "next_step": "texte", "assessment": "texte", "overall_tier": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "lead_time_tier": "texte", "metrics_assessed": 1, "affiliate_context": {}, "computation_basis": "texte", "deploy_frequency_tier": "texte"}} - ec2-cost-calculator≈ 511 tokens
Use when a user asks about EC2 cost. Given instance type and hours, returns monthly cost and DO-equivalent savings estimate.
Paramètres, retour & exemple (3)
Paramètresos· string · optionnel
os used by this deterministic tool.instance_type· string · requis
instance type used by this deterministic tool.hours_per_month· number · optionnel
hours per month used by this deterministic tool.
Exemple d'appel{"name": "ec2-cost-calculator", "arguments": {"instance_type": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "do_savings": 1, "annual_cost": 1, "hourly_rate": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte"}} - egress-cost-calculator≈ 648 tokens
Use this when a user asks about monthly internet egress cost from daily request volume, average response size, provider, and CDN offload. Uses the same model as the browser calculator.
Paramètres, retour & exemple (4)
Paramètrescdn_pct· number · optionnel
cdn expressed as a percentage.provider· string · optionnel · AWS | GCP | Azure | Cloudflare | DigitalOcean
Cloud provider whose published pricing model should be applied.daily_requests· number · requis
daily requests used by this deterministic tool.avg_response_kb· number · requis
avg response kb used by this deterministic tool.
Exemple d'appel{"name": "egress-cost-calculator", "arguments": {"daily_requests": 1, "avg_response_kb": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cdn_pct": 1, "provider": "texte", "cost_risk": "texte", "next_step": "texte", "rate_per_gb": 1, "free_tier_gb": 1, "next_step_url": "texte", "why_follow_up": "texte", "cdn_offload_gb": 1, "interpretation": "texte", "daily_egress_gb": 1, "monthly_cost_usd": 1}} - error-budget-calculator≈ 546 tokens
Use this when a user asks about their SLO error budget, remaining error budget, or burn rate. Given SLO percentage and window, returns budget minutes remaining, burn rate multiplier, and status (Under budget / Elevated / ALERTING).
Paramètres, retour & exemple (4)
Paramètresslo_pct· number · requis
Service-level objective target expressed as a percentage.window_days· number · optionnel
Length of the service-level objective window in days.consumed_minutes· number · optionnel
consumed in minutes.window_elapsed_days· number · optionnel
window elapsed days used by this deterministic tool.
Exemple d'appel{"name": "error-budget-calculator", "arguments": {"slo_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "burn_rate": 1, "next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "budget_minutes": 1, "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte", "remaining_minutes": 1}} - incident-cost-calculator≈ 572 tokens
Use this when a user asks what an outage or incident cost, or wants to calculate the financial impact of downtime. Takes hourly revenue, downtime duration, and affected percentage. Returns revenue impact, engineering cost, and total incident cost in dollars.
Paramètres, retour & exemple (5)
Paramètreseng_hourly· number · optionnel
eng hourly used by this deterministic tool.responders· number · optionnel
responders used by this deterministic tool.affected_pct· number · optionnel
affected expressed as a percentage.downtime_hours· number · requis
downtime in hours.hourly_revenue· number · requis
hourly revenue used by the calculation; monetary values are in USD unless stated otherwise.
Exemple d'appel{"name": "incident-cost-calculator", "arguments": {"downtime_hours": 1, "hourly_revenue": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"severity": "texte", "next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "total_cost_usd": 1, "affiliate_context": {}, "computation_basis": "texte", "revenue_impact_usd": 1, "engineering_cost_usd": 1}} - known-vulnerability-checker≈ 473 tokens
Historical curated package-name advisory reference only. Matches older CVE examples for common packages; does not query live feeds or evaluate installed version ranges, so it never proves a package is currently vulnerable or safe.
Paramètres, retour & exemple (1)
Paramètrespackage_name· string · requis
Package identifier, optionally with a version (e.g. lodash@4.17.21, log4j-core, @babel/core). Versions are not assessed by this historical lookup.
Exemple d'appel{"name": "known-vulnerability-checker", "arguments": {"package_name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cve": "texte", "status": "texte", "severity": "texte", "next_step": "texte", "package_name": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "checked_against": "texte", "affiliate_context": {}, "computation_basis": "texte"}} - kubernetes-manifest-linter≈ 464 tokens
Lint a Kubernetes manifest (YAML) for common issues: missing resource limits, missing health checks, :latest tag usage, privileged containers. Returns issue list and severity.
Paramètres, retour & exemple (1)
Paramètresmanifest· string · requis
Kubernetes manifest YAML content
Exemple d'appel{"name": "kubernetes-manifest-linter", "arguments": {"manifest": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"issues": [], "severity": "texte", "next_step": "texte", "issue_count": 1, "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte"}} - mttr-calculator≈ 474 tokens
Use when a user asks about MTTR or DORA recovery time. Takes incident timestamps (string lines "start,detected,resolved" or array of {start,detected,resolved}).
Paramètres, retour & exemple (1)
Paramètresincidents· ? · requis
incidents used by this deterministic tool.
Exemple d'appel{"name": "mttr-calculator", "arguments": {"incidents": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "dora_rating": "texte", "output_tier": "texte", "mttd_minutes": 1, "mttr_minutes": 1, "signal_value": 1, "next_step_url": "texte", "remaining_pct": 1, "why_follow_up": "texte", "incident_count": 1, "interpretation": "texte", "affiliate_context": {}}} - on-call-burden-calculator≈ 582 tokens
Use when a user asks about on-call load or burnout risk. Uses team size, rotation length, and hourly rate exactly as the browser calculator does.
Paramètres, retour & exemple (3)
Paramètresteam_size· number · requis
team size used by this deterministic tool.hourly_rate· number · requis
hourly rate used by the calculation; monetary values are in USD unless stated otherwise.rotation_weeks· number · requis
rotation weeks used by this deterministic tool.
Exemple d'appel{"name": "on-call-burden-calculator", "arguments": {"team_size": 1, "hourly_rate": 1, "rotation_weeks": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "annual_cost": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "remaining_pct": 1, "why_follow_up": "texte", "interpretation": "texte", "pct_working_time": 1, "affiliate_context": {}, "computation_basis": "texte"}} - pipeline-cost-calculator≈ 718 tokens
Use this when a user asks how much their GitHub Actions CI/CD pipeline costs per month. Takes average job duration in minutes, jobs per run, runs per month and the runner label (ubuntu-latest, windows-latest, macos-latest or self-hosted; matched case-insensitively). Uses GitHub list prices for standard hosted runners effective 1 Jan 2026 and GitHub Free's 2,000 included minutes for private repositories, drawn at list price. Self-hosted minutes carry no GitHub charge.
Paramètres, retour & exemple (4)
Paramètresrunner· string · optionnel
Runner label, for example ubuntu-latest, windows-latest, macos-latest or self-hosted. Matched case-insensitively; defaults to Linux.avg_job_min· number · requis
Average job duration in minutes.jobs_per_run· number · requis
Jobs per workflow run.runs_per_month· number · requis
Workflow runs per month.
Exemple d'appel{"name": "pipeline-cost-calculator", "arguments": {"avg_job_min": 1, "jobs_per_run": 1, "runs_per_month": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"severity": "texte", "next_step": "texte", "rates_as_of": "texte", "runner_type": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "billable_minutes": 1, "included_minutes": 1, "monthly_cost_usd": 1, "affiliate_context": {}, "computation_basis": "texte"}} - precision-recall-f1-calculator≈ 534 tokens
Use this when a user asks about their ML model precision, recall, F1 score, or F-beta score. Takes precision and recall as fractions from 0 to 1 and an optional beta weight. Returns F1, F-beta, and interpretation of the precision-recall tradeoff.
Paramètres, retour & exemple (3)
Paramètresbeta· number · optionnel
beta used by this deterministic tool.recall· number · requis
recall used by this deterministic tool.precision· number · requis
precision used by this deterministic tool.
Exemple d'appel{"name": "precision-recall-f1-calculator", "arguments": {"recall": 1, "precision": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"beta": 1, "f1_score": 1, "next_step": "texte", "f_beta_score": 1, "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte", "precision_recall_gap": 1, "precision_recall_balance": "texte"}} - query-cost-estimator≈ 611 tokens
Estimate PostgreSQL sequential-scan and index-scan cost from table rows, table pages, selectivity, and storage type. Uses the same four-input model as the browser calculator.
Paramètres, retour & exemple (4)
Paramètrestable_rows· number · requis
table rows used by this deterministic tool.table_pages· number · requis
table pages used by this deterministic tool.storage_type· string · requis · ssd | nvme | hdd | network
storage type; accepted values: ssd, nvme, hdd, network.selectivity_pct· number · requis
selectivity expressed as a percentage.
Exemple d'appel{"name": "query-cost-estimator", "arguments": {"table_rows": 1, "table_pages": 1, "storage_type": "ssd", "selectivity_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "cost_ratio": 1, "index_pages": 1, "index_tuples": 1, "storage_type": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "index_scan_cost": 1, "random_page_cost": 1, "recommended_plan": "texte", "affiliate_context": {}}} - rate-limit-utilization-calculator≈ 507 tokens
Calculate API rate limit utilization given current request count and limit. Returns utilization percentage, buffer, safety status, and risk level (OK at <80%, WARNING at 80-95%, CRITICAL at >95%).
Paramètres, retour & exemple (3)
Paramètreslimit· number · requis
Rate limit ceilingwindow_seconds· number · optionnel
Rate limit window in seconds (e.g. 60 for per-minute)current_requests· number · requis
Current request count in the window
Exemple d'appel{"name": "rate-limit-utilization-calculator", "arguments": {"limit": 1, "current_requests": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"safe": true, "buffer": 1, "status": "texte", "next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "window_seconds": 1, "utilization_pct": 1, "affiliate_context": {}, "computation_basis": "texte"}} - reserved-instance-breakeven≈ 734 tokens
Use this when a user asks whether to buy Reserved Instances or stay on On-Demand, or how long an RI takes to pay for itself. Takes On-Demand and RI monthly costs plus optional upfront fees (0 when omitted). Judges the 1-year and 3-year terms separately and returns each break-even month and net saving. It recommends a term only when that term saves money over its own length, and prefers 3 years only when it beats three 1-year terms over 36 months at current prices.
Paramètres, retour & exemple (5)
Paramètresod_monthly· number · requis
On-Demand cost per month in USD.ri_1yr_monthly· number · requis
1-year Reserved Instance cost per month in USD, excluding the upfront fee.ri_1yr_upfront· number · optionnel
1-year upfront fee in USD; 0 when omitted (no-upfront RI).ri_3yr_monthly· number · requis
3-year Reserved Instance cost per month in USD, excluding the upfront fee.ri_3yr_upfront· number · optionnel
3-year upfront fee in USD; 0 when omitted (no-upfront RI).
Exemple d'appel{"name": "reserved-instance-breakeven", "arguments": {"od_monthly": 1, "ri_1yr_monthly": 1, "ri_3yr_monthly": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"severity": "texte", "next_step": "texte", "next_step_url": "texte", "why_follow_up": "texte", "interpretation": "texte", "breakeven_months": 1, "recommended_term": "texte", "affiliate_context": {}, "computation_basis": "texte", "net_savings_1yr_usd": 1, "net_savings_3yr_usd": 1, "breakeven_months_3yr": 1}} - rightsizing-calculator≈ 665 tokens
Use when a user asks about instance rightsizing or overprovisioned compute.
Paramètres, retour & exemple (6)
Paramètreshourly_cost· number · optionnel
hourly cost used by the calculation; monetary values are in USD unless stated otherwise.p99_cpu_pct· number · requis
p99 cpu expressed as a percentage.current_vcpu· number · requis
current vcpu used by this deterministic tool.instance_count· number · optionnel
instance count used by this deterministic tool.p99_memory_pct· number · requis
p99 memory expressed as a percentage.current_memory_gb· number · requis
current memory in gigabytes.
Exemple d'appel{"name": "rightsizing-calculator", "arguments": {"p99_cpu_pct": 1, "current_vcpu": 1, "p99_memory_pct": 1, "current_memory_gb": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "do_savings": 1, "needed_vcpu": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "why_follow_up": "texte", "annual_savings": 1, "instance_count": 1, "interpretation": "texte", "savings_factor": 1}} - slo-burn-rate-calculator≈ 581 tokens
Use this when a user asks how fast they are burning their error budget, or whether their current error rate will exhaust their SLO window. Takes error count, total requests, SLO target, and observation window. Returns burn rate and budget consumption per hour.
Paramètres, retour & exemple (4)
Paramètresslo· number · requis
Service-level objective target expressed as a percentage.total· number · requis
Total number of requests observed in the measurement window.errors· number · requis
Number of failed requests observed in the measurement window.window_hours· number · requis
Length of the observed measurement window in hours.
Exemple d'appel{"name": "slo-burn-rate-calculator", "arguments": {"slo": 1, "total": 1, "errors": 1, "window_hours": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "burn_rate": 1, "next_step": "texte", "window_hours": 1, "next_step_url": "texte", "why_follow_up": "texte", "error_rate_pct": 1, "interpretation": "texte", "affiliate_context": {}, "computation_basis": "texte", "budget_consumed_pct_per_hour": 1}} - software-purchase-risk-calculator≈ 800 tokens
Use when a user asks about risk of a software purchase or SaaS commitment.
Paramètres, retour & exemple (8)
ParamètresnumUsers· number · optionnel
numUsers used by this deterministic tool.setupHours· number · optionnel
setupHours used by this deterministic tool.integrationCount· number · optionnel
integrationCount used by this deterministic tool.internalHourlyCost· number · optionnel
internalHourlyCost used by this deterministic tool.monthlySubscription· number · requis
monthlySubscription used by this deterministic tool.changeManagementRisk· number · optionnel
changeManagementRisk used by this deterministic tool.contractLengthMonths· number · optionnel
contractLengthMonths used by this deterministic tool.vendorStabilityScore· number · optionnel
vendorStabilityScore used by this deterministic tool.
Exemple d'appel{"name": "software-purchase-risk-calculator", "arguments": {"monthlySubscription": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "risk_score": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "why_follow_up": "texte", "contract_total": 1, "interpretation": "texte", "year1_sub_cost": 1, "contract_months": 1, "vendor_component": 1}} - terraform-plan-cost-estimator≈ 504 tokens
Use when a user asks to estimate monthly cost of a Terraform plan.
Paramètres, retour & exemple (3)
Paramètrescount· number · requis
count used by this deterministic tool.instance_size· string · optionnel
instance size used by this deterministic tool.resource_type· string · requis
resource type used by this deterministic tool.
Exemple d'appel{"name": "terraform-plan-cost-estimator", "arguments": {"count": 1, "resource_type": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "annual_cost": 1, "hourly_rate": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "resource_type": "texte", "why_follow_up": "texte", "interpretation": "texte", "resource_count": 1, "affiliate_context": {}}} - total-cost-of-ownership-calculator≈ 808 tokens
Use when a user asks about TCO or multi-year SaaS cost.
Paramètres, retour & exemple (8)
ParamètresoneTimeFees· number · optionnel
oneTimeFees used by this deterministic tool.numPaidSeats· number · requis
numPaidSeats used by this deterministic tool.contractLength· number · optionnel
contractLength used by this deterministic tool.perUserMonthlyFee· number · optionnel
perUserMonthlyFee used by this deterministic tool.adminHoursPerMonth· number · optionnel
adminHoursPerMonth used by this deterministic tool.expectedActiveUsers· number · requis
expectedActiveUsers used by this deterministic tool.internalHourlyCost105· number · optionnel
internalHourlyCost105 used by this deterministic tool.baseMonthlySubscription· number · optionnel
baseMonthlySubscription used by this deterministic tool.
Exemple d'appel{"name": "total-cost-of-ownership-calculator", "arguments": {"numPaidSeats": 1, "expectedActiveUsers": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"next_step": "texte", "do_savings": 1, "output_tier": "texte", "monthly_cost": 1, "signal_value": 1, "next_step_url": "texte", "why_follow_up": "texte", "contract_total": 1, "interpretation": "texte", "seat_waste_pct": 1, "contract_months": 1, "shelfware_seats": 1}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».