Skip to main content
Glama

get-accounts

Retrieve all Autodesk Construction Cloud accounts available through the APS MCP Server to manage project access and permissions.

Instructions

List all available Autodesk Construction Cloud accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get-accounts' tool. It authenticates using getAccessToken, fetches hubs (accounts) via DataManagementClient, and returns formatted account info.
    export const getAccounts: Tool<typeof schema> = {
        title: "get-accounts",
        description: "List all available Autodesk Construction Cloud accounts",
        schema,
        callback: async () => {
            const accessToken = await getAccessToken(["data:read"]);
            const dataManagementClient = new DataManagementClient();
            const hubs = await dataManagementClient.getHubs({ accessToken });
            if (!hubs.data) {
                throw new Error("No accounts found");
            }
            return {
                content: hubs.data.map((hub) => ({
                    type: "text",
                    text: JSON.stringify({ id: hub.id, name: hub.attributes?.name })
                }))
            };
        }
    };
  • src/server.ts:12-14 (registration)
    Generic registration loop that registers all tools exported from './tools/index.js', including 'get-accounts', with the MCP server.
    for (const tool of Object.values(tools)) {
        server.tool(tool.title, tool.description, tool.schema, tool.callback);
    }
  • src/tools/index.ts:1-1 (registration)
    Barrel export re-exporting the getAccounts tool from its implementation file for convenient import in server.ts.
    export { getAccounts } from "./get-accounts.js";
  • Empty input schema definition for the 'get-accounts' tool (no parameters required).
    const schema = {};
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 a read operation ('List') but lacks details on permissions, rate limits, pagination, or return format. This is a significant gap for a tool with zero annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple list operation.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'accounts' entail (e.g., user accounts, project accounts), the return format, or any behavioral traits, making it inadequate for a tool that might have complexity in data retrieval.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately does not discuss parameters, earning a baseline score of 4 for not adding unnecessary details beyond the schema.

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 verb ('List') and resource ('Autodesk Construction Cloud accounts'), making the purpose evident. However, it does not differentiate from sibling tools like 'get-projects' or 'get-issues', which also list resources but target different entities, so it lacks explicit sibling distinction.

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. It does not mention context, prerequisites, or exclusions, such as whether it's for initial setup or general account management, leaving usage unclear relative to siblings like 'get-projects'.

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

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