Skip to main content
Glama
severity1

terraform-cloud-mcp

get_organization_details

Retrieve comprehensive organization information including settings, contact details, and configuration defaults from Terraform Cloud.

Instructions

Get details for a specific organization

Retrieves comprehensive information about an organization including settings, email contact info, and configuration defaults.

API endpoint: GET /organizations/{organization}

Args: organization: The organization name to retrieve details for (required)

Returns: Organization details including name, email, settings and configuration

See: docs/tools/organization.md for reference documentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYes

Implementation Reference

  • The main handler function that executes the tool logic by making an API request to retrieve organization details from Terraform Cloud.
    @handle_api_errors
    async def get_organization_details(organization: str) -> APIResponse:
        """Get details for a specific organization
    
        Retrieves comprehensive information about an organization including settings,
        email contact info, and configuration defaults.
    
        API endpoint: GET /organizations/{organization}
    
        Args:
            organization: The organization name to retrieve details for (required)
    
        Returns:
            Organization details including name, email, settings and configuration
    
        See:
            docs/tools/organization.md for reference documentation
        """
        request = OrganizationDetailsRequest(organization=organization)
        return await api_request(f"organizations/{request.organization}")
  • Pydantic input schema model defining and validating the 'organization' parameter for the tool.
    class OrganizationDetailsRequest(APIRequest):
        """Request model for getting organization details.
    
        This model is used for the GET /organizations/{name} endpoint. The endpoint
        returns detailed information about an organization including its name,
        external ID, created date, and all organization-level settings.
    
        Reference: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/organizations#show-an-organization
    
        See:
            docs/models/organization.md for reference
        """
    
        organization: str = Field(
            ...,
            # No alias needed as field name matches API field name
            description="The name of the organization to retrieve details for",
            min_length=3,
            pattern=r"^[a-z0-9][-a-z0-9_]*[a-z0-9]$",
        )
  • Registers the get_organization_details tool with the MCP server using the FastMCP tool decorator.
    mcp.tool()(organizations.get_organization_details)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a retrieval operation ('Get/Retrieves'), which implies read-only behavior, but doesn't explicitly confirm this or mention any side effects, authentication requirements, rate limits, or error conditions. The mention of an API endpoint ('GET /organizations/{organization}') hints at HTTP semantics but doesn't elaborate on behavioral traits.

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?

The description is well-structured and appropriately sized. It front-loads the purpose, provides additional context in the second sentence, and includes structured sections for Args and Returns. The 'See' reference is useful but could be considered slightly extraneous. Overall, most sentences earn their place without unnecessary verbosity.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is moderately complete. It covers the purpose, parameter, and return scope adequately. However, for a tool with no annotations, it lacks details on behavioral aspects like error handling, authentication, or rate limits, which would improve completeness for agent usage.

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?

The schema description coverage is 0%, but the description compensates by documenting the single parameter: 'organization: The organization name to retrieve details for (required).' This adds meaning beyond the schema's basic type definition. However, it doesn't provide format details (e.g., string constraints, examples) or explain what constitutes a valid organization name, leaving some ambiguity.

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 clearly states the tool's purpose: 'Get details for a specific organization' and 'Retrieves comprehensive information about an organization including settings, email contact info, and configuration defaults.' This specifies the verb ('Get/Retrieves'), resource ('organization'), and scope of information returned. However, it doesn't explicitly differentiate from sibling tools like 'get_account_details' or 'get_project_details' beyond the resource name.

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?

The description provides no guidance on when to use this tool versus alternatives. While it mentions retrieving details for 'a specific organization,' it doesn't clarify when to use this versus 'list_organizations' or 'get_organization_entitlements.' There's no mention of prerequisites, context, or exclusions for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/severity1/terraform-cloud-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server