Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

get_account

Read-only

Retrieve detailed account information from Octopus Deploy by providing the space name and account ID. Use this tool to access account data for DevOps management and troubleshooting.

Instructions

Get details for a specific account by its ID

This tool retrieves detailed information about a specific account using its ID. The space name and account ID are both required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYes
accountIdYesThe ID of the account to retrieve

Implementation Reference

  • The core handler function for the 'get_account' tool. It fetches the Octopus Deploy client configuration, resolves the space ID, retrieves the account resource via API, maps it to a simplified structure, and returns it as JSON-formatted text content.
    async ({ spaceName, accountId }) => {
      const configuration = getClientConfigurationFromEnvironment();
      const client = await Client.create(configuration);
      const spaceId = await resolveSpaceId(client, spaceName);
    
      const response = await client.get<AccountResource>(
        "~/api/{spaceId}/accounts/{id}",
        {
          spaceId,
          id: accountId,
        }
      );
    
      const account = mapAccountResource(response);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(account),
          },
        ],
      };
    }
  • Input schema using Zod validation for the tool parameters: spaceName (string) and accountId (string with description).
    {
      spaceName: z.string(),
      accountId: z.string().describe("The ID of the account to retrieve"),
    },
  • Primary registration of the 'get_account' tool on the MCP server within the registerGetAccountTool function, including name, description, input schema, output metadata, and handler reference.
      server.tool(
        "get_account",
        `Get details for a specific account by its ID
    
    This tool retrieves detailed information about a specific account using its ID. The space name and account ID are both required.`,
        {
          spaceName: z.string(),
          accountId: z.string().describe("The ID of the account to retrieve"),
        },
        {
          title: "Get a specific account by ID from an Octopus Deploy space",
          readOnlyHint: true,
        },
        async ({ spaceName, accountId }) => {
          const configuration = getClientConfigurationFromEnvironment();
          const client = await Client.create(configuration);
          const spaceId = await resolveSpaceId(client, spaceName);
    
          const response = await client.get<AccountResource>(
            "~/api/{spaceId}/accounts/{id}",
            {
              spaceId,
              id: accountId,
            }
          );
    
          const account = mapAccountResource(response);
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(account),
              },
            ],
          };
        }
      );
    }
  • Self-registration of the get_account tool into the central TOOL_REGISTRY, specifying toolset and read-only config for conditional enabling in index.ts.
    registerToolDefinition({
      toolName: "get_account",
      config: { toolset: "accounts", readOnly: true },
      registerFn: registerGetAccountTool,
    });
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds context about required parameters (spaceName and accountId) and that it retrieves 'detailed information,' which goes beyond the annotations. However, it doesn't disclose behavioral traits like rate limits, error handling, or what 'detailed information' entails, leaving some gaps.

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 front-loaded with the main purpose in the first sentence, followed by a clarifying sentence. It's appropriately sized with no wasted words, though it could be slightly more structured to highlight key points like differentiation from siblings.

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 complexity (simple read operation), annotations cover safety, and no output schema exists, the description is adequate but incomplete. It mentions retrieving 'detailed information' but doesn't specify what that includes, and it lacks guidance on error cases or usage relative to siblings, leaving room for improvement.

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?

Schema description coverage is 50%, with only 'accountId' having a description. The description adds that 'space name and account ID are both required,' which clarifies parameter necessity but doesn't provide additional meaning beyond the schema's required field. Since schema coverage is moderate, the description compensates minimally, aligning with the baseline.

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 account by its ID' and 'retrieves detailed information about a specific account using its ID.' It specifies the verb ('get'/'retrieve') and resource ('account'), but doesn't explicitly differentiate from sibling tools like 'list_accounts' or other 'get_' tools beyond mentioning the ID requirement.

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

Usage Guidelines3/5

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

The description implies usage context by stating 'The space name and account ID are both required,' which suggests prerequisites. However, it doesn't explicitly state when to use this tool versus alternatives like 'list_accounts' or other 'get_' tools, nor does it provide exclusions or specific scenarios.

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/OctopusDeploy/mcp-server'

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