Skip to main content
Glama
lastping-dev

LastPing

by lastping-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Export Terraform configuration

export_terraform
Read-onlyIdempotent

Export existing monitors, destinations, routes, alert templates, and status pages as Terraform HCL with import blocks to adopt them into infrastructure-as-code without recreating.

Instructions

Requires the read scope or higher. Exports existing monitors, destinations, routes, alert templates and status pages as Terraform HCL, with import blocks so they are adopted rather than recreated. Secrets are not exported; the output references Terraform variables that hold them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional tag to filter monitors by, e.g. 'agent:claude'. Only monitors carrying this tag (and their routes/templates) are exported.
includeNoOptional comma-separated subset of monitors,destinations,routes,templates,status_pages. Omitted: everything.
monitor_slugNoOptional slug to export a single monitor by. Combines with tag if both are given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedInput schema / properties / include / description
      Previous value: -"Optional comma-separated subset of monitors,destinations,routes,templates,status_pages. Omit to export everything."New value: +"Optional comma-separated subset of monitors,destinations,routes,templates,status_pages. Omitted: everything."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes beyond them by disclosing that secrets are omitted and surfaced as Terraform variable references, and that import blocks exist to adopt rather than recreate resources — real behavioral context an agent could not infer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences; the permission prerequisite is front-loaded, followed by scope, then the secret-handling caveat. No filler and every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by characterizing the return (HCL plus import blocks, secrets replaced by variable references) and the auth requirement. Nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so tag, include, and monitor_slug are fully documented in the schema. The description contributes no additional parameter semantics beyond what the schema already states, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (Exports) plus enumerated resources (monitors, destinations, routes, alert templates, status pages) and the output format (Terraform HCL). No sibling tool does export, so it is trivially distinguishable from the create/update/list/delete family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States a prerequisite ('Requires the read scope or higher') and frames the intended outcome (adopted rather than recreated). It does not name when-not to use it or point at a sibling alternative, but for a unique export capability that guidance is largely unnecessary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools