Skip to main content
Glama

get-issues

Retrieve and list issues from a specified Autodesk Construction Cloud project to track and manage construction-related problems and tasks.

Instructions

List all available projects in an Autodesk Construction Cloud account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • The main handler implementation for the 'get-issues' tool, including title, description, schema, and the async callback that processes the projectId, obtains an access token, strips 'b.' prefix, fetches issues via IssuesClient, and returns formatted content.
    export const getIssues: Tool<typeof schema> = {
        title: "get-issues",
        description: "List all available projects in an Autodesk Construction Cloud account",
        schema,
        callback: async ({ projectId }) => {
            // TODO: add pagination support
            const accessToken = await getAccessToken(["data:read"]);
            const issuesClient = new IssuesClient();
            projectId = projectId.replace("b.", ""); // the projectId should not contain the "b." prefix
            const issues = await issuesClient.getIssues(projectId, { accessToken });
            if (!issues.results) {
                throw new Error("No issues found");
            }
            return {
                content: issues.results.map((issue) => ({ type: "text", text: JSON.stringify(issue) }))
            };
        }
    };
  • Input schema definition using Zod, requiring a non-empty string projectId.
    const schema = {
        projectId: z.string().nonempty()
    };
  • src/server.ts:12-14 (registration)
    Generic registration loop that registers the 'get-issues' tool (imported as part of tools) with the MCP server using server.tool().
    for (const tool of Object.values(tools)) {
        server.tool(tool.title, tool.description, tool.schema, tool.callback);
    }
  • src/tools/index.ts:5-5 (registration)
    Re-export of the getIssues tool object from its source file, enabling its inclusion in the server's tools import.
    export { getIssues } from "./get-issues.js";
  • Shared helper function to retrieve a cached APS access token for given scopes, called within the get-issues handler.
    export async function getAccessToken(scopes: string[]): Promise<string> {
        const cacheKey = scopes.join("+");
        let credentials = credentialsCache.get(cacheKey);
        if (!credentials || credentials.expiresAt < Date.now()) {
            const { access_token, expires_in } = await getServiceAccountAccessToken(APS_CLIENT_ID!, APS_CLIENT_SECRET!, APS_SA_ID!, APS_SA_KEY_ID!, APS_SA_PRIVATE_KEY!, scopes);
            credentials = {
                accessToken: access_token,
                expiresAt: Date.now() + expires_in * 1000
            };
            credentialsCache.set(cacheKey, credentials);
        }
        return credentials.accessToken;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions listing projects, which implies a read-only operation, but doesn't disclose any behavioral traits like permissions needed, rate limits, or response format. The description adds minimal value beyond the implied action.

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

Conciseness3/5

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

The description is a single, clear sentence, but it's front-loaded with incorrect information. While concise, the structural issue of misalignment with the tool name undermines its effectiveness. It earns some credit for brevity but loses points for accuracy.

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

Completeness1/5

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

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain the tool's actual function, parameters, or return values. The mismatch with the tool name makes it inadequate for a tool with one required parameter and complex sibling context.

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

Parameters1/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. It mentions 'Autodesk Construction Cloud account' but doesn't explain the 'projectId' parameter or its role. The description fails to add any meaning beyond the schema, leaving the parameter undocumented and confusing given the tool's stated purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List all available projects' but the tool name is 'get-issues', creating a direct contradiction. This is misleading as it suggests the tool retrieves projects rather than issues. The description fails to state what the tool actually does and misaligns with the tool name.

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

Usage Guidelines1/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. With sibling tools like 'get-projects' and 'get-issue-comments', the description offers no context for differentiation. The mismatch between name and description further confuses usage 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/petrbroz/aps-mcp-server'

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