Skip to main content
Glama

get-projects

Retrieve a list of all projects in your Autodesk Construction Cloud account to manage construction data and workflows efficiently.

Instructions

List all available projects in an Autodesk Construction Cloud account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYes

Implementation Reference

  • The asynchronous callback function that executes the core logic of the 'get-projects' tool. It authenticates using getAccessToken, initializes DataManagementClient, retrieves projects for the specified accountId, and returns a content array with JSON-formatted project details.
    callback: async ({ accountId }) => {
        // TODO: add pagination support
        const accessToken = await getAccessToken(["data:read"]);
        const dataManagementClient = new DataManagementClient();
        const projects = await dataManagementClient.getHubProjects(accountId, { accessToken });
        if (!projects.data) {
            throw new Error("No projects found");
        }
        return {
            content: projects.data.map((project) => ({
                type: "text",
                text: JSON.stringify({ id: project.id, name: project.attributes?.name })
            }))
        };
    }
  • Zod schema defining the input parameters for the tool, specifically requiring a non-empty string for 'accountId'.
    const schema = {
        accountId: z.string().nonempty()
    };
  • src/server.ts:11-14 (registration)
    Creates the MCP server instance and registers all tools (including 'get-projects') imported from './tools/index.js' using a loop over Object.values(tools), passing title, description, schema, and callback to server.tool().
    const server = new McpServer({ name: "autodesk-platform-services", version: "0.0.1" });
    for (const tool of Object.values(tools)) {
        server.tool(tool.title, tool.description, tool.schema, tool.callback);
    }
  • src/tools/index.ts:2-2 (registration)
    Re-exports the getProjects tool from its implementation file, making it available for bulk import in server.ts via './tools/index.js'.
    export { getProjects } from "./get-projects.js";
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it lists projects without behavioral details. It doesn't disclose if this is a read-only operation, what permissions are needed, how results are returned (e.g., pagination, sorting), or any rate limits. The description is minimal and lacks critical context for safe invocation.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse. Every part of the sentence contributes to understanding the tool's purpose.

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 tool has no annotations, no output schema, and low schema coverage, the description is incomplete. It covers the basic purpose but misses behavioral traits, parameter details, and output expectations. For a tool with one required parameter and no structured support, more context is needed for effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'accountId' is, how to obtain it, or its format. With 1 required parameter undocumented, the description fails to provide meaningful semantics 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 ('projects'), specifying the scope as 'all available projects in an Autodesk Construction Cloud account'. It distinguishes from siblings like get-accounts or get-issues by focusing on projects, but doesn't explicitly differentiate from potential overlapping tools beyond the resource type.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites like needing an accountId, nor does it compare with other project-related tools that might exist (though none are listed in siblings). Usage is implied by the action but not explicitly framed.

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