Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_terraform_imports

Read-onlyIdempotent

Generates Terraform import blocks for LogicMonitor resource types, enabling you to bring existing portal objects under Terraform management and generate their configuration.

Instructions

List a resource type's portal objects as Terraform import blocks for the logicmonitor/logicmonitor provider, one import { to, id } block per object, for 15 of the provider resource types that import by ID; cluster alert confs are left out, since the API refuses the read the provider's importer makes. Run terraform init, then terraform plan -generate-config-out=generated.tf on the blocks to have Terraform write the resource configuration. The provider authenticates with LMv1 api_id and api_key only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource_type": "<resource_type>"
    },
    "name": "get_terraform_imports"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
filterNoLogicMonitor filter expression, sent as written
offsetNoPagination offset
resource_typeYesProvider resource type, without the logicmonitor_ prefix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: one block emitted per object, the exact downstream Terraform commands required, the auth constraint (LMv1 api_id and api_key only), and a documented API limitation that excludes cluster alert confs. That is the kind of context an agent cannot get from the structured fields.

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

Conciseness4/5

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

Front-loaded with what the tool produces, followed by the follow-up commands and the exclusion rationale; every sentence carries information. The opening sentence is long and clause-heavy, which costs a little readability.

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?

For a read-only listing tool with no output schema, the description supplies the return shape, the scope restriction, the auth requirement, and the post-generation workflow. Nothing an agent needs to call it and use the result correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema carries the parameter docs; the description still adds meaning by explaining that `resource_type` is restricted to the 15 provider types that import by ID, which explains the enum's composition rather than restating it. `limit`, `filter`, and `offset` get no extra treatment, but they are fully documented in the schema.

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?

States a specific verb and resource (list a resource type's portal objects) plus the exact output shape: `import { to, id }` blocks for the logicmonitor/logicmonitor provider. It also scopes the tool to the 15 provider resource types that import by ID, which separates it cleanly from the plain get_* list siblings.

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?

Gives clear usage context: generate blocks, then run `terraform init` and `terraform plan -generate-config-out=generated.tf`. It also names one exclusion (cluster alert confs, because the API refuses the importer's read). It stops short of routing the agent to a sibling list tool when raw JSON rather than Terraform blocks is wanted.

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