Release v0.9.6: Simplify Terraform Registry API Interactions

- Removed `exampleConfigGenerator` tool
- Simplified tool interfaces by removing unused parameters
- Updated tools to use direct documentation links instead of complex API parsing
- Improved error handling and tool resilience
- Updated tests to reflect tool changes
- Removed fallback patterns in favor of direct documentation links
- Updated README.md and api-use.md to reflect tool changes
- Clarified required and optional parameters in documentation

Author: thrashr888

.cursorrules

@@ -2,7 +2,7 @@
 - update the version in index.ts and package.json
 - update the CHANGELOG.md
 - commit, tag, and push to GitHub
-- create a new release on GitHub
+- create a new release on GitHub using `gh`
 - npm and docker releases are handled automatically via GitHub Actions
 - `npm i -g terraform-mcp-server` to globally install/update the CLI
 
@@ -13,3 +13,4 @@
 - run `./test.sh` to run the tests
 - run `./test-simple.sh` to run the tests
 - locally managed MCP config is in `./.cursor/mcp.json` and `~/Library/Application Support/Claude/claude_desktop_config.json`
+- ./api-use.md has examples of how to use the API

CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.9.6 (May 21, 2024)
+- Removed `exampleConfigGenerator` tool
+- Simplified tool interface by removing unused parameters
+- Updated tests to reflect tool changes
+- Simplified `dataSourceLookup` function to use documentation URL directly
+- Simplified `resourceArgumentDetails` function to use documentation URL directly
+- Fixed 404 errors in test-simple.sh script
+- Made tools more resilient to Terraform Registry API changes
+- Removed fallback patterns in favor of simpler, more reliable direct documentation links
+- Updated README.md to reflect removal of `exampleConfigGenerator` tool
+- Updated api-use.md to document current API usage patterns
+- Clarified required and optional parameters in documentation
+- Improved documentation formatting and examples
+
 ## 0.9.5 (April 23, 2024)
 - Fixed `exampleConfigGenerator` function to handle API changes from HashiCorp Registry
 - Added fallback approach that uses documentation URLs to generate example configs

README.md

@@ -70,9 +70,9 @@ Looks up Terraform provider details by name, returning the latest version and ve
 
 ```json
 {
-  "provider": "aws",             // Optional: Provider name
+  "provider": "aws",             // Required: Provider name
   "namespace": "hashicorp",      // Optional: Provider namespace (defaults to "hashicorp")
-  "name": "aws"                  // Optional: Alternative field for provider name
+  "version": "latest"            // Optional: Provider version
 }
 ```
 
@@ -97,9 +97,8 @@ Gets example usage of a Terraform resource and related resources.
 
 ```json
 {
-  "provider": "aws",             // Optional: Provider name
-  "resource": "aws_instance",    // Optional: Resource name
-  "name": "aws_instance"         // Optional: Alternative field for resource name
+  "provider": "aws",             // Required: Provider name
+  "resource": "aws_instance"     // Required: Resource name
 }
 ```
 
@@ -124,8 +123,7 @@ Searches for and recommends Terraform modules based on a query.
 
 ```json
 {
-  "query": "vpc",                // Optional: Search query
-  "keyword": "vpc",              // Optional: Alternative field for search query
+  "query": "vpc",                // Required: Search query
   "provider": "aws"              // Optional: Filter modules by provider
 }
 ```
@@ -169,37 +167,7 @@ Retrieves available data source identifiers for a given Terraform provider.
 }
 ```
 
-### 5. Provider Schema Details
-
-Retrieves full schema details of a provider, including resource and data source schemas.
-
-**Input:**
-
-```json
-{
-  "provider": "aws",             // Required: Provider name
-  "namespace": "hashicorp"       // Required: Provider namespace
-}
-```
-
-**Output:**
-
-```json
-{
-  "content": [{
-    "type": "text",
-    "text": {
-      "provider_schema": {
-        "provider_schemas": { ... },
-        "resource_schemas": { ... },
-        "data_source_schemas": { ... }
-      }
-    }
-  }]
-}
-```
-
-### 6. Resource Argument Details
+### 5. Resource Argument Details
 
 Fetches comprehensive details about a specific resource type's arguments, including required and optional attributes, nested blocks, and their descriptions.
 
@@ -240,7 +208,7 @@ BLOCKS:
 For full documentation, visit: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance
 ```
 
-### 7. Module Details
+### 6. Module Details
 
 Retrieves detailed metadata for a Terraform module.
 
@@ -283,35 +251,6 @@ Retrieves detailed metadata for a Terraform module.
 }
 ```
 
-### 8. Example Configuration Generator
-
-Generates a minimal Terraform configuration for a given provider and resource.
-
-**Input:**
-
-```json
-{
-  "provider": "aws",             // Required: Provider name
-  "namespace": "hashicorp",      // Required: Provider namespace
-  "resource": "aws_instance"     // Required: Resource name
-}
-```
-
-**Output:**
-
-```json
-{
-  "content": [
-    {
-      "type": "text",
-      "text": {
-        "example_configuration": "resource \"aws_instance\" \"example\" {\n  ami = \"example\"\n  instance_type = \"example\"\n}\n"
-      }
-    }
-  ]
-}
-```
-
 ## Running the Server
 
 The server runs using stdio transport for MCP communication:

api-use.md

@@ -17,13 +17,13 @@ This document outlines our understanding and use of the Terraform Registry API f
 ### Resource Endpoints
 
 - **Resource Details**: `https://registry.terraform.io/v1/providers/{namespace}/{provider}/resources/{resource}`
-  - Used in `resourceArgumentDetails` and `exampleConfigGenerator` tools
+  - Used in `resourceArgumentDetails`
   - This endpoint has been reported as returning 404 errors
   - We now use a fallback approach when this fails
 
 - **Resource Documentation**: `https://registry.terraform.io/providers/{namespace}/{provider}/latest/docs/resources/{resource}`
-  - Used as a fallback in `exampleConfigGenerator` when the API endpoint fails
   - HTML documentation page that can be parsed for examples
+  - Used for retrieving resource details when API endpoints fail
 
 ### Module Endpoints
 
@@ -37,17 +37,13 @@ This document outlines our understanding and use of the Terraform Registry API f
 
 ## API Changes and Issues
 
-As of version 0.9.5, we've encountered some issues with the Terraform Registry API:
+As of version 0.9.6, we've encountered some issues with the Terraform Registry API:
 
 1. **Resource Details Endpoint Failures**:
    - The `/v1/providers/{namespace}/{provider}/resources/{resource}` endpoint often returns 404 errors
    - We've implemented fallbacks using documentation URLs to handle these failures
 
-2. **Example Configuration Generation**:
-   - Direct API methods for retrieving example configurations are unreliable
-   - We've implemented a fallback approach that parses documentation pages for examples
-
-3. **Provider Schema Access**:
+2. **Provider Schema Access**:
    - When API endpoints fail, we attempt to download the provider schema directly
    - This provides a complete schema but requires additional processing
 
@@ -56,7 +52,7 @@ As of version 0.9.5, we've encountered some issues with the Terraform Registry A
 When API endpoints fail, we employ these fallback strategies:
 
 1. **Documentation URL Parsing**:
-   - For example configurations, we fall back to scraping the documentation
+   - For resource details, we fall back to using the documentation URL directly
    - URLs follow the pattern: `https://registry.terraform.io/providers/{namespace}/{provider}/latest/docs/resources/{resource}`
 
 2. **Provider Schema Download**: