Skip to main content
Glama

aps_issues_docs

Retrieve ACC Issues API quick-reference documentation covering project ID format, statuses, workflow, API paths, filters, sort options, and error troubleshooting. Call this before your first Issues interaction.

Instructions

Return ACC Issues API quick‑reference documentation: project ID format, statuses, typical workflow, raw API paths, common filters, sort options, and error troubleshooting. Call this before your first Issues interaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:785-794 (registration)
    Tool registration for 'aps_issues_docs' in the TOOLS array. Defines name, description, and empty inputSchema (no parameters).
    // 18 ── aps_issues_docs
    {
      name: "aps_issues_docs",
      description:
        "Return ACC Issues API quick‑reference documentation: " +
        "project ID format, statuses, typical workflow, raw API paths, " +
        "common filters, sort options, and error troubleshooting. " +
        "Call this before your first Issues interaction.",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • Tool handler for 'aps_issues_docs' – simply returns the ISSUES_DOCS constant wrapped in an ok() response.
    // ── aps_issues_docs ─────────────────────────────────────────
    if (name === "aps_issues_docs") {
      return ok(ISSUES_DOCS);
    }
  • The ISSUES_DOCS constant containing the full quick-reference documentation string (project ID format, statuses, workflow, raw API paths, filters, sort options, error troubleshooting).
    export const ISSUES_DOCS = `# ACC Issues API – Quick Reference
    
    ## Important: Project ID Format
    The Issues API uses project IDs **without** the 'b.' prefix.
    - Data Management ID: \`b.a4be0c34a-4ab7\`
    - Issues API ID:      \`a4be0c34a-4ab7\`
    
    The simplified tools handle this conversion automatically – you can pass either format.
    
    ## Statuses
    \`draft\` → \`open\` → \`pending\` / \`in_progress\` / \`in_review\` / \`completed\` / \`not_approved\` / \`in_dispute\` → \`closed\`
    
    ## Typical Workflow
    \`\`\`
    1. aps_issues_get_types     project_id                     → get issue categories & types
    2. aps_issues_list          project_id + filters           → browse issues
    3. aps_issues_get           project_id + issue_id          → single issue details
    4. aps_issues_create        project_id + title + subtype   → create new issue
    5. aps_issues_update        project_id + issue_id + fields → update issue
    6. aps_issues_get_comments  project_id + issue_id          → read comments
    7. aps_issues_create_comment project_id + issue_id + body  → add comment
    \`\`\`
    
    ## Raw API Paths (for aps_issues_request)
    | Action | Method | Path |
    |--------|--------|------|
    | User profile | GET | construction/issues/v1/projects/{projectId}/users/me |
    | Issue types | GET | construction/issues/v1/projects/{projectId}/issue-types?include=subtypes |
    | Attribute definitions | GET | construction/issues/v1/projects/{projectId}/issue-attribute-definitions |
    | Attribute mappings | GET | construction/issues/v1/projects/{projectId}/issue-attribute-mappings |
    | Root cause categories | GET | construction/issues/v1/projects/{projectId}/issue-root-cause-categories?include=rootcauses |
    | List issues | GET | construction/issues/v1/projects/{projectId}/issues |
    | Create issue | POST | construction/issues/v1/projects/{projectId}/issues |
    | Get issue | GET | construction/issues/v1/projects/{projectId}/issues/{issueId} |
    | Update issue | PATCH | construction/issues/v1/projects/{projectId}/issues/{issueId} |
    | List comments | GET | construction/issues/v1/projects/{projectId}/issues/{issueId}/comments |
    | Create comment | POST | construction/issues/v1/projects/{projectId}/issues/{issueId}/comments |
    
    ## Common Filters (for aps_issues_list)
    - \`filter[status]\` – open, closed, pending, in_progress, etc.
    - \`filter[assignedTo]\` – Autodesk user/company/role ID
    - \`filter[issueTypeId]\` – category UUID
    - \`filter[issueSubtypeId]\` – type UUID
    - \`filter[dueDate]\` – YYYY-MM-DD
    - \`filter[createdAt]\` – YYYY-MM-DDThh:mm:ss.sz
    - \`filter[search]\` – search by title or display ID
    - \`filter[locationId]\` – LBS location UUID
    - \`filter[rootCauseId]\` – root cause UUID
    - \`filter[displayId]\` – chronological issue number
    
    ## Sort Options
    \`createdAt\`, \`updatedAt\`, \`displayId\`, \`title\`, \`status\`, \`assignedTo\`, \`dueDate\`, \`startDate\`, \`closedAt\`
    Prefix with \`-\` for descending (e.g. \`-createdAt\`).
    
    ## Region Header (x-ads-region)
    Possible values: \`US\` (default), \`EMEA\`, \`AUS\`, \`CAN\`, \`DEU\`, \`IND\`, \`JPN\`, \`GBR\`.
    Pass as the \`region\` parameter on any Issues tool.
    
    ## Creating an Issue (required fields)
    - \`title\` – the issue title (max 10,000 chars)
    - \`issueSubtypeId\` – the type UUID (get from aps_issues_get_types)
    - \`status\` – initial status (e.g. 'open')
    
    ## Error Troubleshooting
    | Code | Common Cause | Fix |
    |------|-------------|-----|
    | 401 | Expired / invalid token | Check credentials; token auto‑refreshes |
    | 403 | App not provisioned or insufficient scopes | Admin → Account Settings → Custom Integrations. Ensure scope includes 'data:read data:write' for write operations |
    | 404 | Wrong project ID or issue not found | Ensure project ID has no 'b.' prefix for raw API calls |
    | 409 | Conflict (e.g. duplicate) | Check for existing resource |
    | 422 | Attachment limit reached (100/issue) | Remove old attachments first |
    
    ## Full Specification
    - OpenAPI: https://github.com/autodesk-platform-services/aps-sdk-openapi/blob/main/construction/issues/Issues.yaml
    `;
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does not disclose that the tool is read‑only or that it has no side effects, but the nature of returning documentation implies safety. Some behavioral context is missing, but it is not contradictory.

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 two sentences with no wasted words. The purpose and usage hint are front‑loaded, making it easy to parse quickly. Every sentence earns its place.

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 the tool has no parameters, no output schema, and no annotations, the description sufficiently covers its function and when to use it. It could specify the output format (e.g., text, structured) but is otherwise complete for its intended role as a reference tool.

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 input schema has zero parameters, so the description bears no obligation to explain them. Per rubric, 0 parameters yields a baseline of 4. The description adds value by specifying the content of the documentation, which is relevant to the agent's understanding.

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?

The description uses a specific verb ('Return') and resource ('ACC Issues API quick‑reference documentation') and lists detailed content (project ID format, statuses, workflow, etc.). It clearly distinguishes from sibling tools like aps_issues_list or aps_issues_get, which perform operations rather than provide reference.

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

Usage Guidelines4/5

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

Explicitly states 'Call this before your first Issues interaction,' providing clear usage context. While it does not mention when not to use it or name alternatives, the directive is sufficient for initial guidance.

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