Skip to main content
Glama

aps_issues_request

Issue raw HTTP requests to the ACC Issues API for full control over endpoints, custom filters, attribute definitions, and attribute mappings. Use when simplified tools do not cover your needs. Requires project ID without 'b.' prefix.

Instructions

Call any ACC Issues API endpoint (construction/issues/v1). This is the raw / power‑user tool – it returns the full API response. Prefer the simplified tools (aps_issues_list, aps_issues_get, etc.) for everyday use. Use this when you need full control: custom filters, attribute definitions, attribute mappings, or endpoints not covered by simplified tools.

⚠️ Project IDs for the Issues API must NOT have the 'b.' prefix. If you have a Data Management project ID like 'b.abc123', use 'abc123'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesHTTP method.
pathYesAPI path relative to developer.api.autodesk.com (e.g. 'construction/issues/v1/projects/{projectId}/issues'). Must include the version prefix (construction/issues/v1).
queryNoOptional query parameters as key/value pairs (e.g. { "filter[status]": "open", "limit": "50" }).
bodyNoOptional JSON body for POST/PATCH requests.
regionNoData centre region (x-ads-region header). Defaults to US.

Implementation Reference

  • src/index.ts:378-422 (registration)
    Tool registration and input schema definition for 'aps_issues_request' - defines name, description, and inputSchema (method, path, query, body, region) in the TOOLS array.
    {
      name: "aps_issues_request",
      description:
        "Call any ACC Issues API endpoint (construction/issues/v1). " +
        "This is the raw / power‑user tool – it returns the full API response. " +
        "Prefer the simplified tools (aps_issues_list, aps_issues_get, etc.) for everyday use. " +
        "Use this when you need full control: custom filters, attribute definitions, attribute mappings, " +
        "or endpoints not covered by simplified tools.\n\n" +
        "⚠️ Project IDs for the Issues API must NOT have the 'b.' prefix. " +
        "If you have a Data Management project ID like 'b.abc123', use 'abc123'.",
      inputSchema: {
        type: "object" as const,
        properties: {
          method: {
            type: "string",
            enum: ["GET", "POST", "PATCH", "DELETE"],
            description: "HTTP method.",
          },
          path: {
            type: "string",
            description:
              "API path relative to developer.api.autodesk.com " +
              "(e.g. 'construction/issues/v1/projects/{projectId}/issues'). " +
              "Must include the version prefix (construction/issues/v1).",
          },
          query: {
            type: "object",
            description:
              "Optional query parameters as key/value pairs " +
              "(e.g. { \"filter[status]\": \"open\", \"limit\": \"50\" }).",
            additionalProperties: { type: "string" },
          },
          body: {
            type: "object",
            description: "Optional JSON body for POST/PATCH requests.",
          },
          region: {
            type: "string",
            enum: ["US", "EMEA", "AUS", "CAN", "DEU", "IND", "JPN", "GBR"],
            description: "Data centre region (x-ads-region header). Defaults to US.",
          },
        },
        required: ["method", "path"],
      },
    },
  • Handler function for 'aps_issues_request' tool - extracts method/path/query/body/region from args, validates path, builds headers, and calls apsDmRequest to execute the raw Issues API call.
    // ── aps_issues_request ──────────────────────────────────────
    if (name === "aps_issues_request") {
      const method = (args.method as string) ?? "GET";
      const path = args.path as string;
      const pathErr = validateIssuesPath(path);
      if (pathErr) return fail(pathErr);
    
      const query = args.query as Record<string, string> | undefined;
      const body = args.body as Record<string, unknown> | undefined;
      const region = args.region as string | undefined;
      const t = await token();
    
      const headers: Record<string, string> = {
        ...issuesHeaders(region),
      };
      if ((method === "POST" || method === "PATCH") && body !== undefined) {
        headers["Content-Type"] = "application/json";
      }
    
      const data = await apsDmRequest(
        method as "GET" | "POST" | "PATCH" | "DELETE",
        path,
        t,
        { query, body, headers },
      );
      return json(data);
    }
  • Helper validator validateIssuesPath() used by the aps_issues_request handler to validate the path parameter.
    export function validateIssuesPath(path: string): string | null {
      if (!path || typeof path !== "string")
        return "path is required and must be a non‑empty string.";
      if (path.includes("..")) return "path must not contain '..'.";
      return null;
    }
  • Helper function issuesHeaders() used by the handler to build x-ads-region header for Issues API calls.
    function issuesHeaders(region?: string): Record<string, string> {
      const h: Record<string, string> = {};
      if (region) h["x-ads-region"] = region;
      return h;
    }
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states it returns the full API response and warns about project ID format, but does not disclose details about authentication, rate limiting, error handling, or side effects. For a raw API tool, more transparency could be added.

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?

Description is concise—two short paragraphs and a bulleted warning. Every sentence serves a purpose, no fluff. The first sentence immediately establishes the tool's purpose.

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

Completeness4/5

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

Given there is no output schema, the description covers the return value by noting it returns the full API response. It mentions applicable endpoints and custom filters. It is mostly complete for the tool's intended power-user use case, though it could touch on potential error scenarios or quota implications.

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?

Input schema has 100% coverage with descriptions for all 5 parameters. The description adds value by clarifying the path format (must include version prefix) and providing the project ID prefix warning, which is not evident from the schema alone. This extra guidance justifies a score above baseline.

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

Purpose5/5

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

Description clearly states it calls any ACC Issues API endpoint and returns the full API response. It contrasts with simplified tools like aps_issues_list, aps_issues_get, etc., specifying the tool's role as a power-user alternative.

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

Usage Guidelines5/5

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

Explicitly advises to prefer simplified tools for everyday use and provides specific scenarios for using this tool (custom filters, attribute definitions, endpoints not covered). Also includes a critical warning about omitting the 'b.' prefix for project IDs.

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/EverseDevelopment/APS.MCP'

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