Tools and Language Support

Available Tools (Reference)

Your MCP client discovers tools automatically when it connects. Use this page as a quick reference, and use your client’s tool discovery (tools/list) as the source of truth for what’s available right now.

Tool	Description	When to use	What to provide	Example
`get_available_products`	Returns the canonical Autodesk product catalog (closed set).	When you need the exact values for product filters (and supported releases).	No parameters.	`{"name":"get_available_products","arguments":{}}`
`search_help_content`	Searches Autodesk Help/Support documentation and returns the most relevant documents for a question.	How‑to guidance, troubleshooting (including error messages), and official reference content across Autodesk products.	Required: `query`, `locale` (details) Optional: `product_code` / `product_name`, `release_code`, `sources`, `max_results`	`{"name":"search_help_content","arguments":{"query":"AutoCAD Plant 3D spec editor add property set","locale":"en_US","max_results":5}}`

For an end-to-end workflow, see Autodesk Product Help MCP Server (Recommended flow + Common Workflows).

search_help_content inputs (reference)

Required

Parameter	Type	Description
`query`	string	Keyword-rich. Include product + task/feature, and exact error codes/messages when relevant. Min length 2.
`locale`	string	Locale used to scope search/results (language/region). Use the locale from the user’s context (do not guess).

Optional

Parameter	Type	Description
`product_code`	string	Preferred product filter. Use an exact value returned by `get_available_products`.
`product_name`	string	Alternative product filter. Use an exact value returned by `get_available_products`.
`release_code`	string	Product-specific release identifier. Only pass an exact value returned for the resolved product.
`sources`	string[]	Restrict which sources to search (for example `sfdc_articles`, `product_documentation`). Omit to search all.
`max_results`	integer	Maximum number of results to return. Default is 5.

Tips for successful tool calls

Goal	Recommendation
Avoid invalid product filters	Treat product values as a closed set: use exact values returned by `get_available_products` (don’t normalize or change casing).
Reduce ambiguity	Prefer `product_code` over `product_name` when both are accepted.
Use releases correctly	`release_codes` are codes only (for example `"2025"`), not human-readable names (for example `"AutoCAD 2025"`).
Avoid guesswork	If you can’t confidently map a request to an allowed value (product/release/locale), omit the field and retry. For required `locale`, use the locale from context (do not guess).
Keep requests safe	Don’t include sensitive data in queries (credentials, secrets, personal data).

Multi-Language Support

The server supports multiple languages for search and retrieval. In tool calls, language is typically expressed as a locale (for example en_US, fr_FR, zh_CN) and validated by the tool schema.

Note:

Some older Autodesk Help examples use 3-letter language codes (for example ENU, DEU). If you encounter those, you can usually map them to a locale like this:

Locale (tool input)	Language	Autodesk Help language code (examples)
`en_US`	English (United States)	`ENU`
`fr_FR`	French (France)	`FRA`
`de_DE`	German (Germany)	`DEU`
`es_ES`	Spanish (Spain)	`ESP`
`pt_BR`	Portuguese (Brazil)	`PTB`
`it_IT`	Italian (Italy)	`ITA`
`ja_JP`	Japanese (Japan)	`JPN`
`ko_KR`	Korean (Korea)	`KOR`
`zh_CN`	Chinese (Simplified)	`CHS`
`ru_RU`	Russian (Russia)	`RUS`

How to set language:

Conversationally (recommended): tell your client what language/locale to use in your request. Example: "Search help content for 'viewport' in German."
Tool inputs (when exposed): some tools take a locale input (for example en_US). If your client asks you for a locale, use the value it expects (do not guess).