Skip to main content
Glama
env0

env0

Official
by env0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Cloud Resources

get-cloud-resources

Retrieve and filter cloud resources from env0 by provider, type, region, account, severity, drift status, or management type to inspect or manage your cloud inventory.

Instructions

Get cloud resources from env0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagingNo
filtersYes
orderByNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.1.3
    • changedInput schema / properties / filters / properties / cloudConfigurationId / description
      Previous value: -"The cloud configuration ID, can be found using the Cloud Configurations tool. It's required that you provide either a configuration ID or a cloud provider"New value: +"The cloud configuration ID, can be found using the Cloud Configurations tool. Scopes the search to a single cloud configuration"
    • removedInput schema / properties / filters / properties / cloudConfigurationId / properties / in
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / filters / properties / cloudConfigurationId / required
      Added value: +[
+  "eq"
+]
    • changedInput schema / properties / filters / properties / cloudProvider / description
      Previous value: -"The cloud provider ID. It's required that you provide either a configuration ID or a cloud provider"New value: +"The cloud provider to search in. Defaults to the only provider the organization has, so it is only needed when the organization has more than one and no configuration ID is given"
    • removedInput schema / properties / filters / properties / cloudProvider / properties / in
      Removed value: -{
-  "items": {
-    "$ref": "#/properties/filters/properties/cloudProvider/properties/eq"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / filters / properties / cloudProvider / required
      Added value: +[
+  "eq"
+]
    • changedInput schema / properties / filters / properties / driftStatus / $ref
      Previous value: -"#/properties/filters/properties/cloudConfigurationId"New value: +"#/properties/filters/properties/managementType"
    • removedInput schema / properties / filters / properties / managementType / $ref
      Removed value: -"#/properties/filters/properties/cloudConfigurationId"
    • addedInput schema / properties / filters / properties / managementType / additionalProperties
      Added value: +false
    • addedInput schema / properties / filters / properties / managementType / properties
      Added value: +{
+  "eq": {
+    "type": "string"
+  },
+  "in": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / filters / properties / managementType / type
      Added value: +"object"
    • changedInput schema / properties / filters / properties / name / $ref
      Previous value: -"#/properties/filters/properties/cloudConfigurationId"New value: +"#/properties/filters/properties/managementType"
    • changedInput schema / properties / filters / properties / region / $ref
      Previous value: -"#/properties/filters/properties/cloudConfigurationId"New value: +"#/properties/filters/properties/managementType"
    • changedInput schema / properties / filters / properties / service / $ref
      Previous value: -"#/properties/filters/properties/cloudConfigurationId"New value: +"#/properties/filters/properties/managementType"
    • changedInput schema / properties / filters / properties / type / $ref
      Previous value: -"#/properties/filters/properties/cloudConfigurationId"New value: +"#/properties/filters/properties/managementType"
  2. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral disclosure. 'Get' implies a read operation, but the description says nothing about permissions, whether it is read-only, pagination behavior, rate limits, or how results are returned.

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

Conciseness3/5

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

The description is a single concise sentence and is front-loaded. However, it is too terse for the tool's complexity and does not earn its brevity by conveying any necessary scoping or usage information.

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

Completeness2/5

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

For a complex tool with nested objects, required filters, no annotations, and no output schema, the description is substantially incomplete. It does not explain the filtering model, pagination, ordering, or expected return behavior, leaving the agent to infer too much from the schema alone.

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

Parameters2/5

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

The description adds no meaning for the three top-level parameters: paging, filters, and orderBy. Although the schema contains some nested filter descriptions, top-level schema description coverage is reported at 0%, and the description does not compensate by explaining what filters are required or how paging/orderBy should be used.

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

Purpose4/5

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

The description gives a clear verb and resource ('Get cloud resources') and identifies the env0 domain. However, it does not distinguish this tool from sibling retrieval tools such as get-cloud-configurations or get-environments, and it omits any scope such as filtering or pagination.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many sibling tools. It does not state prerequisites, when filters are required, or how it relates to tools like get-cloud-configurations.

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