> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# List Agent Functions

> Use the list_agent_functions MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="read-only"><Badge color="gray" size="sm" shape="pill">Read only</Badge></span>

Returns the tool/function definitions (e.g. transfer call, book appointment, custom API calls) configured on a specific agent version. Credential-shaped config values (API keys, tokens, auth headers) are redacted. Use get\_agent\_version first if you don't already have the version\_number.

## Parameters

| Name             | Type     | Required | Description                      |
| ---------------- | -------- | -------- | -------------------------------- |
| `agent_id`       | `string` | Yes      | The agent ID, e.g. agent\_abc123 |
| `version_number` | `string` | Yes      | The version number, e.g. 1       |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* Provide the required parameters: `agent_id`, `version_number`.

## Example MCP request

Send `tools/call` after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_agent_functions",
    "arguments": {
      "agent_id": "agent_abc123",
      "version_number": "1"
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/errors) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`, parse `content[0].text` as JSON, and verify that returned IDs and workspace data match the request.

## Retry safety

This tool does not change workspace data. Retrying after a transient transport failure is safe.

## Related MCP tools

* [Get Agent Version](/docs/mcp-tools/agents/get-agent-version): `get_agent_version`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Agents MCP tools](/docs/mcp-tools/agents/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)