Loading ToolBench
Terraform provider for the Agyn platform, enabling infrastructure-as-code management of agents, apps, installations, environments, and other Agyn resources
This is not an MCP server, it is a Terraform provider. The submission appears to be categorized incorrectly. The codebase uses terraform-plugin-framework (HashiCorp's standard for Terraform providers) and exposes resources (agyn_app, agyn_app_installation) via Terraform's resource interface, not MCP tools. MCP servers operate over HTTP/SSE/STDIO with the MCP protocol; this provider operates over Terraform's plugin protocol (gRPC-based). Tool definitions are inferred from resource names in the file paths and partial API wrapper code, not explicitly visible in the source provided. Parameter schemas cannot be verified from the code sample (only partial API client code is shown). Descriptions are minimal or inferred. No error handling patterns visible in samples. This fundamentally fails the MCP evaluation framework.
Manages an Agyn app.
Manages an Agyn app installation.
Not an MCP server. This is a Terraform provider using terraform-plugin-framework, not an MCP implementation. Transport is gRPC-based plugin protocol, not HTTP/SSE/STDIO.
Tool definitions inferred from file paths and partial API code. Actual resource schema definitions (required_attributes, optional_attributes, computed_attributes, attribute types) not visible in the provided source. Cannot verify input schema completeness or parameter type annotations.
Tool descriptions are one-line resource descriptions ('Manages an Agyn app.', 'Manages an Agyn app installation.'). These are far below the 50 - 200 character production baseline and do not explain WHEN to use the tool, WHAT it does in terms of side effects (create/update/delete/read), or WHAT it returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 29 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 38 | - | v1 |
Parameter descriptions provided in the schema summary are bare type descriptions (e.g., 'UUID identifier of the app', 'Organization identifier for the app'). They do not explain constraints (format, length, allowed values, relationships to other parameters), what the parameter controls, or when it is optional vs required.
No error handling documentation visible. No recovery guidance, error categorization (retryable vs user-fixable vs fatal), or actionable error messages shown in the code sample.
agyn_app exposes 'service_token' as an output field. If this is a secret or authentication credential, it must NOT be returned in responses, tokens leak into logs and prompt history.
No permission gates, scope declarations, or audit logging visible. Destructive operations (delete) on agyn_app have no confirmation step or permission checks shown.
agyn_app_installation has a 'configuration' parameter that accepts a free-form JSON string. No validation, format specification, or schema is documented. This invites hallucinated or malformed JSON from agents.
agyn_app 'visibility' enum lists only 'public' and 'internal', but no guidance on defaults, how to change visibility after creation, or what permissions each grants. Underdocumented enums cause agent confusion.