Skip to main content
Glama
Sign In
ACC MCP

ACC MCP

by nhantruong96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

acc_copy_file

Copies a file version into another folder of the same project as a new document, enabling WIP to Shared or Published hand-offs.

Instructions

Copy a file version into another folder of the same project as a NEW document — the typical WIP → Shared / Published hand-off when not using an ACC review workflow. (ACC cannot move items via API; copy then delete the original in the UI if a move is required.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "version_id": "<version_id>",
      "target_folder_id": "<target_folder_id>"
    },
    "name": "acc_copy_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameNoDisplay name for the copy (default: same as source)
project_idYesProject id
version_idYesSource version URN to copy (usually the tip version)
target_folder_idYesDestination folder URN (same project)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With only readOnlyHint=false in annotations, the description adds valuable behavioral context: it creates a 'NEW document' (no overwrite) and explains the API limitation for moves. It does not fully detail side effects like metadata preservation, but it goes beyond what annotations provide.

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?

Two sentences, front-loaded with the core action, followed by a critical constraint. No filler or repetition. Every sentence adds value.

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 an output schema exists and all params are documented, the description sufficiently explains the tool's purpose, use case, and a key API limitation. It doesn't explain every edge case (like preserving custom attributes) but is complete for typical usage.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description does not add parameter-specific details, but it reinforces context like 'same project' and 'NEW document'. This meets the baseline for full schema coverage.

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+resource+outcome ('Copy a file version into another folder of the same project as a NEW document') and clearly distinguishes from siblings by mentioning the WIP → Shared/Published hand-off. It is not a tautology and fully conveys what the tool does.

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 states when to use it ('typical WIP → Shared / Published hand-off when not using an ACC review workflow') and gives an exclusion/alternative ('when not using an ACC review workflow'). Also clarifies that ACC cannot move items via API, so copy then delete in UI if a move is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools