Skip to main content
Glama

aps_list_submittal_specs

Retrieve specification sections that organize submittal items in an Autodesk Construction Cloud project. Get identifiers, titles, and dates for each spec division, with pagination support.

Instructions

List spec sections for submittals in an ACC project. Returns a compact summary: identifier (e.g. '033100'), title, dates. Spec sections are the specification divisions that submittal items are organised under.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID (UUID or 'b.' prefixed – auto‑converted).
limitNoMax items per page (1–200). Default 20.
offsetNoPagination offset. Default 0.

Implementation Reference

  • src/index.ts:935-960 (registration)
    Registration of the aps_list_submittal_specs tool in the TOOLS array with its name, description, and input schema (project_id, limit, offset).
    // 23 ── aps_list_submittal_specs
    {
      name: "aps_list_submittal_specs",
      description:
        "List spec sections for submittals in an ACC project. " +
        "Returns a compact summary: identifier (e.g. '033100'), title, dates. " +
        "Spec sections are the specification divisions that submittal items are organised under.",
      inputSchema: {
        type: "object" as const,
        properties: {
          project_id: {
            type: "string",
            description: "Project ID (UUID or 'b.' prefixed – auto‑converted).",
          },
          limit: {
            type: "number",
            description: "Max items per page (1–200). Default 20.",
          },
          offset: {
            type: "number",
            description: "Pagination offset. Default 0.",
          },
        },
        required: ["project_id"],
      },
    },
  • Handler function that validates the project ID, builds query parameters (limit/offset), calls the Submittals API 'specs' endpoint via apsDmRequest, and formats the result via summarizeSubmittalSpecs.
    // ── aps_list_submittal_specs ────────────────────────────────
    if (name === "aps_list_submittal_specs") {
      const projectId = args.project_id as string;
      const e1 = validateSubmittalProjectId(projectId);
      if (e1) return fail(e1);
    
      const query: Record<string, string> = {};
      const limit = Math.min(Math.max(Number(args.limit) || 20, 1), 200);
      query.limit = String(limit);
      if (args.offset != null) query.offset = String(args.offset);
    
      const t = await token();
      const raw = await apsDmRequest("GET", submittalPath(projectId, "specs"), t, {
        query,
        headers: { "Content-Type": "application/json" },
      });
      return json(summarizeSubmittalSpecs(raw));
    }
  • Type definition for a spec section summary returned by the tool, with fields: id, identifier, title, created_at, updated_at.
    export interface SubmittalSpecSummary {
      id: string;
      identifier: string;
      title: string;
      created_at?: string;
      updated_at?: string;
    }
  • Helper function that parses the raw API response from GET /specs, extracts pagination info, and maps each result to a SubmittalSpecSummary object.
    /** Summarise the paginated response from GET /specs. */
    export function summarizeSubmittalSpecs(raw: unknown): {
      pagination: { total: number; limit: number; offset: number };
      specs: SubmittalSpecSummary[];
    } {
      const r = raw as Record<string, unknown> | undefined;
      const pagination = r?.pagination as Record<string, unknown> | undefined;
      const results = Array.isArray(r?.results)
        ? (r!.results as Record<string, unknown>[])
        : [];
    
      const specs: SubmittalSpecSummary[] = results.map((spec) => ({
        id: spec.id as string,
        identifier: (spec.identifier as string) ?? "",
        title: (spec.title as string) ?? "(untitled)",
        created_at: (spec.createdAt as string) ?? undefined,
        updated_at: (spec.updatedAt as string) ?? undefined,
      }));
    
      return {
        pagination: {
          total: (pagination?.totalResults as number) ?? specs.length,
          limit: (pagination?.limit as number) ?? 0,
          offset: (pagination?.offset as number) ?? 0,
        },
        specs,
      };
    }
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 that the tool returns a 'compact summary' but does not disclose read-only nature, idempotency, rate limits, or any other behavioral traits beyond the output format.

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, each serving a clear purpose: stating the action and detailing the output. Every word is necessary, and it is front-loaded with the primary verb.

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

Completeness3/5

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

Given no output schema, the description compensates by listing the returned fields. However, it lacks context about pagination behavior (offset semantics) and does not clarify how spec sections relate to submittal items, leaving some ambiguity for complex use cases.

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

Parameters3/5

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

The input schema has 100% description coverage, so parameters are already well-documented. The description adds no additional parameter semantics (e.g., constraints or default behaviors) beyond what the schema provides, earning a baseline score.

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 action ('List spec sections for submittals') and the resource ('in an ACC project'), and explains what is returned. However, it does not differentiate from sibling tools like aps_list_submittal_items, which lists submittal items themselves.

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 implies the tool is for retrieving spec sections but provides no explicit guidance on when to use it over siblings or when not to use it. No alternatives or exclusions are mentioned.

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